Live data from Hacker News

LeakedIn

leakedin.org

151–160 of 194 posts

Re: LeakedIn

#151
post #132

Earlier quoted context omitted.

Ah yes, didn't consider that...you are correct--reset should be forced on login. Though I doubt any of the above will happen. Wouldn't want the user to be inconvenienced now would we?

What is standard practice for a situation like if the users lost access to the email account they signed up with? A large forum I post on was hacked recently and - after voluntarily shutting their site down for a month - they required password resets. If users did not have access to the email address they signed up with and couldn't otherwise verify their identity, they were not allowed to get their account back. Uns…

You can ask for previous passwords, if there are any payments involved you can ask for the transaction ids, obviously if you have secret questions or verified mobile you can ask for that.

Of course all of those things can be used to gain access to the account by attacker, without actually knowing the password. See recent Cloudflare incident. Google will notify you about the recovery attempt, monitor for activity, and delay it for at least a week or so. So the attacker just have to wait till you go on offline vacation ;)

Really though, for something as low key as a forum you’re entirely justified to offer recovery only via email. The email providers already offer all those alternative recovery options. And of course you should prefer OpenID to avoid the issue altogether.

> Unsurprisingly, post counts are down site-wide and the owners have reported a > 25% decrease in traffic.

That’s because they took the site down for a month!

Re: LeakedIn

#152
It is helpful to have a unique password for each meaningful service you use. That way the black-hats can't compromise your other accounts using the same password.

Re: LeakedIn

#153
post #26

I quickly wrote a script to do this locally, not the most efficient, but I'm at work ;) https://github.com/hungtruong/LinkedIn-Password-Checker

I wrote one in Perl as well. I wasn't going to bother uploading it, but I might as well.

https://github.com/rpicard/misc-perl/tree/master/linkedin-pa...

Re: LeakedIn

#155

I 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 :)

Probably a noob question but... How does this account for any salt that may have been used?

Re: LeakedIn

#156

Earlier quoted context omitted.

The Terms and Conditions are hilarious: c. You agree to pay $ 100,000 for your use of the Estatis Free Password Security Checker if we ever ask for it.

"All States shall be entitled to lay submarine cables and pipelines on the bed of the high seas." oh dear.

That's the Geneva convention. It's right after a chapter of Frankenstein.

Re: LeakedIn

#159
post #155

I 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 :)

Probably a noob question but... How does this account for any salt that may have been used?

It doesn't, LinkedIn didn't salt the passwords.

Re: LeakedIn

#160
post #155

I 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 :)

Probably a noob question but... How does this account for any salt that may have been used?

LinkedIn didn't use a salt. Hence the easier-than-it-should-have-been password crackfest.

(However, could everyone please stop making random websites encouraging people to type in their passwords from third party sites!)

Post reply on HN