LeakedIn
leakedin.org
LeakedIn
1–10 of 194 posts
Re: LeakedIn
#2EDIT: Actually never mind, seems like it's much faster now.
Re: LeakedIn
#3You should add a note on the page that lets people know that checking a password takes a minute or two. EDIT: Actually never mind, seems like it's much faster now.
Re: LeakedIn
#4(If we can collect enough data points of whose passwords are on it or not, how old they are, and how complex the password was, we should be able to narrow down a potential date range for the list and the odds that the compromised list is full or partial.)
Re: LeakedIn
#5Re: LeakedIn
#6Mine was not in the list. I had a non-dictionary password with letters and numbers, 8 characters, and it was at least several months old. (If we can collect enough data points of whose passwords are on it or not, how old they are, and how complex the password was, we should be able to narrow down a potential date range for the list and the odds that the compromised list is full or partial.)
Re: LeakedIn
#7Re: LeakedIn
#8Re: LeakedIn
#9I think its safer to test yourself than randomly typing your password in on websites =)
Re: LeakedIn
#10I think its safer to test yourself than randomly typing your password in on websites =)
You can provide your own hash, and a quick source check reveals that plaintext is being converted into a hash client-side, so only hashed data is being sent to the server.