Somebody had the password test123. Lol. I'm going to go see what other crazy simple passwords people have used.
LeakedIn
41–50 of 194 posts
Re: LeakedIn
#42"binladen" was actualy used for a password at linkedin lol!
Re: LeakedIn
#43I quickly wrote a script to do this locally, not the most efficient, but I'm at work ;) https://github.com/hungtruong/LinkedIn-Password-Checker
That works pretty well. And yes, my password is in there.
Re: LeakedIn
#44I'm wondering about the legality of this. If you take an (assumed) stolen dump of sensitive data and turn it into a webservice, could you get in trouble?
Re: LeakedIn
#45Reminds me of the Seinfeld/MovieFone episode...
"Why don't you just tell me your password..."
Re: LeakedIn
#46Earlier quoted context omitted.
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.
So was mypassword and others. Oh well.
Re: LeakedIn
#47I made something almost the same (including name!), except all check is done in browser:
http://crackedin.s3-website-us-east-1.amazonaws.com/
And it's hosted on S3 so it is faster :)
Re: LeakedIn
#48Oh.. Didn't know anyone already made this - i also made a tool, but it doesn't send your whole hash over the wire (only the last 4 chars). http://olemartin.org/linkedin-passwords/
Re: LeakedIn
#49I 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.
Not like they couldn't save it as a variable if they wanted. That's just what you see in the UI.
Re: LeakedIn
#50Your password was leaked, but it has not (yet) been cracked. Fingers crossed.