05.11.2012 Views

Probable Cause Issues in Child Pornography ... - Locatethelaw.org

Probable Cause Issues in Child Pornography ... - Locatethelaw.org

Probable Cause Issues in Child Pornography ... - Locatethelaw.org

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Probable</strong> <strong>Cause</strong> <strong>Issues</strong> <strong>in</strong> <strong>Child</strong> <strong>Pornography</strong> Cases<br />

By Dennis Nicewander, Assistant State Attorney<br />

Page 3 of 48<br />

recognized file's Secured Hash Algorithm value, SHA-1, as one <strong>in</strong>dicat<strong>in</strong>g<br />

child pornography.<br />

State v. Nuss, 279 Neb. 648, 781 N.W.2d 60 (Neb. 2010)<br />

Affidavit was <strong>in</strong>sufficient to establish probable cause for issuance of<br />

warrant to search defendant's residence for evidence of visual depiction of<br />

sexually explicit conduct <strong>in</strong>volv<strong>in</strong>g m<strong>in</strong>ors, where actual downloaded<br />

images <strong>in</strong>tercepted dur<strong>in</strong>g undercover <strong>in</strong>vestigation did not accompany the<br />

affidavit, affidavit did not use or even refer to the statutory def<strong>in</strong>itions of<br />

sexually explicit conduct <strong>in</strong> describ<strong>in</strong>g the <strong>in</strong>tercepted images relied upon<br />

as probable cause for the requested search warrant, but <strong>in</strong>stead referred to<br />

filenames “which are consistent with child pornography” and images<br />

which “appear to be child pornography” without stat<strong>in</strong>g the actual<br />

filenames or describ<strong>in</strong>g the particular conduct depicted <strong>in</strong> the images, and<br />

applicable state crim<strong>in</strong>al statutes, unlike their federal counterparts, did not<br />

<strong>in</strong>clude a def<strong>in</strong>ition of “child pornography.”<br />

Discussion: This was an FBI peer to peer case.<br />

U.S. v. Gen<strong>in</strong>, 594 So.2d 412 (S.D.N.Y 2009)<br />

Search warrant affidavit's reference to defendant's e-mail correspondence with<br />

child pornography website and unnamed Federal Bureau of Investigation<br />

(FBI) analyst's bare and overly broad conclusion that videos referenced by<br />

defendant constituted child pornography was <strong>in</strong>sufficient to establish probable<br />

cause to believe that a search of defendant's apartment would uncover<br />

evidence of child pornography; affidavit did not append, or provide any<br />

description of, the particular videos referenced <strong>in</strong> defendant's e-mail<br />

correspondence with operator of child pornography website, and e-mails<br />

themselves, while sordid, did not describe behavior that fell with<strong>in</strong> any<br />

category of sexually explicit conduct.<br />

Discussion of videos <strong>in</strong> search warrant affidavit was <strong>in</strong>sufficient to establish<br />

probable cause that videos referenced <strong>in</strong> e-mail correspondence between<br />

defendant and operator of child pornography website were lasciviousness, as<br />

required to support search of defendant's apartment; even though affidavit<br />

<strong>in</strong>dicated that “many of the videos” depicted m<strong>in</strong>ors “dressed <strong>in</strong> ‘str<strong>in</strong>g’<br />

l<strong>in</strong>gerie or completely nude, and pos[<strong>in</strong>g] such that their genitals are the focus<br />

of the image,” it rema<strong>in</strong>ed entirely possible that the websites conta<strong>in</strong>ed videos<br />

that fell outside the applicable def<strong>in</strong>itions of child pornography, and there was<br />

no <strong>in</strong>formation l<strong>in</strong>k<strong>in</strong>g the particular videos referenced <strong>in</strong> the e-mail

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!