Hacking Team child porn code
coderman
coderman at gmail.com
Wed Feb 24 04:02:55 PST 2016
On 2/23/16, Travis Biehn <tbiehn at gmail.com> wrote:
> Well,
> The strings for debug code can certainly show up, even these files
> themselves. Which you can see some samples of under /content (the video
> stuff is missing, fueling the conspiracy fire?)
it was meatspin.mov renamed :o
> There's screenshots,
> wallet.dats and fake files. Even a picture of, presumably, one of the
> developers:
> https://github.com/hackedteam/rcs-common/blob/master/lib/rcs-common/evidence/content/camera/001.jpg
:P
> Ref'd:
> https://github.com/hackedteam/rcs-common/blob/master/lib/rcs-common/evidence/camera.rb
>
> In fact, if you look at all the modules in /evidence/ they all contain
> obvious dummy / test data.
E.g. "Show us in a demo, how your software finds the child pr0n, and
sorts it by youngest first, then most disturbing, and queues in a
playlist, for uh, foren-sick analysis" the agent asked while adjusting
the crotch of his navy blue slacks,
so they demo dumb keyword matching and pretend not hear the other part...
> Are they implanting pictures of themselves on hacked machines? Screenshots
> of their own code?
>
> It's obvious to anyone who can take a cursory read of these chunks of code
> in context that this is dummy test data.
not dummy test data, more like for the purposes of a demo data.
otherwise, spot on sir! would read your analysis again++
best regards,
More information about the cypherpunks
mailing list