News for hackers. Stuff that matters.

A comment on LeakedIn. Parent comment

Re:LeakedIn by joshuahedlund on Wednesday June 06, 2012 @03:10PM (#4075573)
Even if you don't check the source code to verify that it's harmless, you should assume your password has been compromised and have already changed it anyway. This just lowers the cost of checking the list and could help us learn more about the compromise.
[ Parent | on HN ]
Re:LeakedIn by shuri on Wednesday June 06, 2012 @05:50PM (#4076397)
If the hole that let them in hasn't been closed yet, changing the password will make that password vulnerable, right?
[ Parent | on HN ]
Re:LeakedIn by Achshar on Wednesday June 06, 2012 @07:58PM (#4076826)
LinkedIn said:

> users who have already changed their passwords or created a new account won’t have to worry, as they have recently begun hashing and salting their current password databases.

http://techcrunch.com/2012/06/06/linkedin-speaks-some-of-tho...

[ Parent | on HN ]
Re:LeakedIn by adavies42 on Wednesday June 06, 2012 @09:26PM (#4077113)
"recently"?!?
[ Parent | on HN ]
Re:LeakedIn by Achshar on Thursday June 07, 2012 @02:48AM (#4077906)
Yes, it could have been a little earlier but from what it seems, it was before the leak.
[ Parent | on HN ]