Live data from Hacker News

LeakedIn

leakedin.org

1–10 of 194 posts

Re: LeakedIn

#2
You 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

#3
post #2

You 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.

Yeah. We got hit pretty hard. It doesn't actually take a minute or two, unless you're doing a few hundred at the same time. Fixing. (-:

Re: LeakedIn

#4
Mine 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

#5
One suggestion: make the input box have a type of 'password'. I was only a bit put-off by seeing my plaintext password staring me in the face!

Re: LeakedIn

#6

Mine 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.)

[deleted]

Re: LeakedIn

#8
Now there's a great idea! Provide your password to some random site purporting to check if your password's been compromised.

Re: LeakedIn

#9
post #7

I 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.

Re: LeakedIn

#10
post #7

I 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.

'password' was actually in use - go figure.
Post reply on HN