• Google to build a cross-industry database of encrypted child porn images
    25 replies, posted
[url]http://www.nbcnews.com/technology/googles-new-plan-combat-internet-child-pornography-6C10331956[/url] [quote]Internet giant Google announced plans Saturday to build a database of encrypted child pornography images to “enable companies, law enforcement and charities to better collaborate on detecting and removing these images, and to take action against the criminals" producing and sharing them. Google is developing the database to be shared with other tech and Internet companies to extend the reach of its newfound anti-child pornography efforts. While tech companies (like Google) individually take action against child pornography, Google's plan is to help all relevant organizations streamline their efforts work by allowing all of them to contribute to the same database and build on one another's work rather than repeating it. To better locate the offending content, Google is using a pre-existing technology known as "hashing," which essentially allows the company to tag images with unique identification codes that can then be reported or blocked by other companies when locating a duplicate image somewhere else on the social Web.[/quote] [url=http://googleblog.blogspot.co.uk/2013/06/our-continued-commitment-to-combating.html]Google's blog post[/url]
So....how long until someone calls Google a bunch of evil pedos and how the FBI has double standards? In all seriousness, Google seems like a good company to do this stuff.
It could work, but a bunch of people are going to make a giant deal out of google hoarding CP
Booby-trapped porn.
[QUOTE=Liem;41070980]It could work, but a bunch of people are going to make a giant deal out of google hoarding CP[/QUOTE] Selfish bastards.
I guess it works off of the appearance of the image itself (like Tineye) rather than the raw data. Re-compressing a CP JPEG would generate an entirely new (conventional) hash.
It's encrypted. Nobody ever sees the pictures except when adding them to the database. Then they already have them. So what's the big deal? This is a great idea to help stop this filth.
[QUOTE=chimitos;41071142]It's encrypted. Nobody ever sees the pictures except when adding them to the database. Then they already have them. So what's the bug deal? This is a great idea to help stop this filth.[/QUOTE] so if a pedo gets the key he's basically hit the motherlode
[QUOTE=trotskygrad;41071160]so if a pedo gets the key he's basically hit the motherlode[/QUOTE] With good hashing you can only compare if two things are similar. You can't get the original back from a hash. [editline]17th June 2013[/editline] It's similar to storing a fingerprint.
[QUOTE=trotskygrad;41071160]so if a pedo gets the key he's basically hit the motherlode[/QUOTE] *and can hack into Google's database. **and is a good enough programmer to decode it This is a query system. You add a new image to the database, tagged as CP. Then websites upload images to the service to see if it matches anything. Its very similar to how spyware scanners work.
[QUOTE=trotskygrad;41071160]so if a pedo gets the key he's basically hit the motherlode[/QUOTE] Yeah I no! Hey, here's some hot porn! I SHA1'd it for you. [code]952efa358436693c5b0b94ccdfe0b95b4ae35918[/code]
@ people telling me how encryption works, yes I know that's probably not what they're doing I'm assuming (in my post) that google used the most rudimentary encryption, and that the database is literally just a collection of files. They're probably not doing that
[quote] To better locate the offending content, Google is using a pre-existing technology known as "hashing," which essentially allows the company to tag images with unique identification codes that can then be reported or blocked by other companies when locating a duplicate image somewhere else on the social Web.[/quote] Well, I'm sure there's much more to the technology than this, as altering just a single bit of the picture would completely change the checksum.
[QUOTE=trotskygrad;41071550]@ people telling me how encryption works, yes I know that's probably not what they're doing I'm assuming (in my post) that google used the most rudimentary encryption, and that the database is literally just a collection of files. They're probably not doing that[/QUOTE] Why would you assume that Google would use the most basic encryption type when dealing with something as serious as this?
[QUOTE=Elecbullet;41071522]Yeah I no! Hey, here's some hot porn! I SHA1'd it for you. Youre sick. [/QUOTE] MODS! CP!
[QUOTE=Lambadvanced;41071636]Why would you assume that Google would use the most basic encryption type when dealing with something as serious as this?[/QUOTE] because it was a half-joke like seriously people.
[QUOTE=Elecbullet;41071522]Yeah I no! Hey, here's some hot porn! I SHA1'd it for you. [code]952efa358436693c5b0b94ccdfe0b95b4ae35918[/code][/QUOTE] dat 9
[QUOTE=trotskygrad;41071160]so if a pedo gets the key he's basically hit the motherlode[/QUOTE] It's like the google version of a kinder surprise egg.
[QUOTE=Ereunity;41072138]It's like the google version of a kinder surprise egg.[/QUOTE] It's tasty and there's fun stuff inside?
binary then base to find the porn!!!! doNT tell tha kops =x= pirate bay production [QUOTE]01100001 01001000 01010010 00110000 01100011 01000100 01101111 01110110 01001100 00110010 01101011 00110010 01001101 01010011 00110101 01110111 01100001 01000111 00111001 00110000 01100010 00110010 01001010 00110001 01011001 00110010 01110100 01101100 01100100 01000011 00110101 01101010 01100010 00110010 00110000 01110110 01011001 01010111 01111000 01101001 01100100 01010111 00110001 01111010 01001100 00110010 01100111 00110010 01001101 01101001 00111001 01101101 01100011 01101101 01010110 01111010 01100001 01000111 01001110 01111001 01100100 01010111 00110101 01110010 01100001 01101110 01010110 01110000 01011001 00110010 01010101 01110110 01001101 01000100 01001001 01110110 01011001 01010111 01100111 01111001 01001100 01101101 01110000 01110111 01011010 01110111 00111101 00111101[/QUOTE]
This could be the ultimate honeypot for catching these people. Once word gets out that there is this huge Google stash of this material and people try to crack it, everyone who tries to access it, or even search for it, will be linked to CP. They could embed some kind of phone home trojan into it and 'leak' a copy, just to follow the trail.
[QUOTE=smurfy;41071702]dat 9[/QUOTE] she looks about 8 years old to me
Well surely they have to have people who's job it is to look at the images and decide whether they are cp or not.
well if someone follows the web requests of this database when it finds cp they could potentially amass the largest collection of CP ever. presumably google would want to continually add new cp to it.
[IMG]http://filesmelt.com/dl/Google-Im-Feeling-Lucky.png[/IMG]
[QUOTE=Elecbullet;41071129]I guess it works off of the appearance of the image itself (like Tineye) rather than the raw data. Re-compressing a CP JPEG would generate an entirely new (conventional) hash.[/QUOTE] I wouldn't really call hashing an encryption. It's so lossy that it barely represents the original picture at all. It just identifies it. It's more of a database of "footprints" of known porn images. The database itself doesn't contain porn at all, and only the people who have to handle it get to work with it.
Sorry, you need to Log In to post a reply to this thread.