On Jun 6, 2012, at 8:10 PM, Moose Finklestein wrote: > > This time they may have said something up front [because the breach is > definite and on their server(s)], but I - well, I would be very cautious.
Yeah, I think it goes without saying that LinkedIn has handled this situation without tact or grace. For a few hours when this first hit today, their Twitter feed said they were "unable to confirm whether a breach had taken place." Somehow, the fact that they were (apparently) unaware that they had been hit is far worse than the fact that they got hit at all. Even compressed, the password hashes are ~107MB; I somehow doubt that the typical LinkedIn user downloads THAT much data on a daily basis? -- Corey
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
