full-disclosure - Re: Facebook

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTimDurBDuzeiJiZxcABGFNbuhWfbvQ@mail.gmail.com>
Date: Wed, 4 May 2011 11:49:09 +0100
From: Michael Simpson <mikie.simpson@...il.com>
To: phil <jabea@...ea.net>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Facebook

On 4 May 2011 04:59, phil <jabea@...ea.net> wrote:
>
> I don’t agree, google is by far the biggest database of what user want and
> look for. If you merge those database (google) and facebook that must make
> some leet profiling. (especially when you think that you can easily find
> where someone live with phone directory and you can match the ip by sector
> too to match the google database)
>

"some leet profiling"
if you look at what netflix (supposedly anonymised) + imdb was able to
do, or the classic of AOL releasing their searches (again anonymised)
then a join of google with facebook is quite a scary prospect.
Especially as d of b + partial zip/postcode allows for
re-identification most of the time (i believe that d of b + state =
85% re-identification).
It wouldn't just be a selective subset but pretty much who, where,
when and probably why without too many non-Amish exceptions.

mike

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/