Earlier quoted context omitted.
The answers to my security questions tend to look like "e74bd7eb-10c6-4b90-bde0-dde2ed64946e"
Your security answer is a software license key?
Or maybe a Windows CLSID.
Yahoo discloses hack of 1B accounts
411–420 of 596 posts
Re: Yahoo discloses hack of 1B accounts
#412Earlier quoted context omitted.
I'm guessing by your handle I know who you are :). Ex-Yahoo super chat moderating guy here, which should let you know me. Wouldn't the upgrade require the accounts to actually login to migrate password? Last I was at Yahoo there was at least 3B junk accounts in UDB. With out knowing details I am guessing that many of the "compromised" accounts fall into that bucket. I get that membership can't just trash junk account…
Just to confirm, purple Yahoo! car in YEF spot ;) As to your question, no, they didn't need to login due to how the hash "upgrade" was done (unlike how Tumblr did it around the same time). I was one of the people in the billion accounts and I definitely have logged in and also changed my password multiple times (also have very high entropy passwords and use TFA).
It wasn't me despite your DR Ycan't photos. :)
Tumblr was indeed what I was thinking about.
Re: Yahoo discloses hack of 1B accounts
#413Earlier quoted context omitted.
It sort of does matter for bcrypt, surprisingly: http://security.stackexchange.com/questions/39849/does-bcryp... In the interests of hewing closest to cryptographic reality, I design not to allow a password longer than the algorithm can usefully use.
This is surprising, do you know how Argon2 behaves compared to this?
Argon2 does the right thing. No silly upper bounds.
Re: Yahoo discloses hack of 1B accounts
#414Earlier quoted context omitted.
Just leave it at passwordpassword, it will be leaked eventually anyway Strong passwords that need to be memorized shouldn't be wasted on security bozos
Why do you assume the password would be leaked eventually? Usually hashes are leaked (as in this case), not passwords.
leaking unsalted md5 passwords == leaking passwords
Re: Yahoo discloses hack of 1B accounts
#415Earlier quoted context omitted.
Just leave it at passwordpassword, it will be leaked eventually anyway Strong passwords that need to be memorized shouldn't be wasted on security bozos
Why do you assume the password would be leaked eventually? Usually hashes are leaked (as in this case), not passwords.
[deleted]
Re: Yahoo discloses hack of 1B accounts
#416I thought we knew about this already, is there more info than before?
This is a separate breach
Re: Yahoo discloses hack of 1B accounts
#417Earlier quoted context omitted.
What do you mean by a password that can't be reasonably brute forced? EDIT: To clarify, I mean specifically with md5. I'm by no means an expert, just curious because I had considered md5 so broken that this comment caught my attention.
Rumours of MD5's death have been greatly exaggerated. MD5's weakness is that it's (relatively) easy to produce two strings which have the same hash. However, given an MD5 hash, it's not easy to produce a string which also has that hash. In principle , one could intentionally construct two passwords which have the same hash. It's hard to see how that could be exploited maliciously - any attacker knows both passwords t…
On a side note: You can use such crafted strings as a black box testing tool to verify if a site does infact use md5 or other weak algorithms to store the passwords. This can perhaps be used in conjunction with other factors to craft an attack.
As a corrollary this can also be used as a testing tool by anyone for any third party site to determine known vulenrablities in their password storage
Re: Yahoo discloses hack of 1B accounts
#418Earlier quoted context omitted.
It sort of does matter for bcrypt, surprisingly: http://security.stackexchange.com/questions/39849/does-bcryp... In the interests of hewing closest to cryptographic reality, I design not to allow a password longer than the algorithm can usefully use.
I think it's best to allow longer passwords for those who use long phrases. It's easier to remember the full phrase than a truncated version. You could show a warning that the extra chars beyond 50-55 will be ignored.
Or you could SHA256 the original password and feed the hash to bcrypt. Remember to use the 64-byte hexadecimal hash, not the 32-byte binary because bcrypt chokes on null bytes.
Everyone's been saying "just use bcrypt", but bcrypt has too many gotchas to be the default choice. We really need to work on getting scrypt and argon2 into the most popular programming languages and frameworks a.s.a.p.
Re: Yahoo discloses hack of 1B accounts
#419Earlier quoted context omitted.
Google also allows you to use google authenticator, but I don't believe they allow third party services.
Google does allow other apps (I think it is still same as GAuth) SASS pass and other authenticators with good. But yes they don't allow other token provides like Yubikey or RSA fobs
> But yes they don't allow other token provides like Yubikey or RSA fobs
I think this is incorrect, at least provided you're using Chrome. The implementation was buggy somewhere in the chain the last time I tried it, but it's there.
Re: Yahoo discloses hack of 1B accounts
#420For the longest time my yahoo account (which I had not checked on in many years) reported at least a dozen open sessions originating from IPs in Russia and Eastern Europe, and unlike my legit sessions I was unable to kill them in the control panel (the site would bug out) So yeah, Yahoo's been hacked. Duh... Finance and Flickr are about all Yahoo is good for any more, and I think my portfolio page loads (instead of 4…
I'm really not sure how they could do flickr more damage than they already have.