4 ms·
EHarmony Confirms Password Hack
- debacle 14y agoWhat a strange week for security.
- Lukeas14 14y agoIf this is part of the same attack that hit LinkedIn and Last.fm are there any theories on what the exploit was? I'm having a hard time imagining how someone could steal passwords from 3 large, completely independent web services at the same time.
- tzs 14y agoIt's possible that these were accumulated at very different times, by very different exploits, and possibly by very different people, and ended up in the hands of one group that released them together. I saw speculation that the easy to break ones have already been long broken and exploited, and this release is the ones that weren't easy. That could explain why all three were dumped at the same time...they basically just went through and dumped the ones they couldn't use from all of the accumulated lists.
- seanp2k2 14y agoSee also: VUPEN hack with 130 0-days supposedly leaked.
- ecaron 14y agoI have to imagine that this will open the potential for a viral website of the "is your spouse still playing the field" variety.
- stcredzero 14y agoCouldn't password databases be implemented as hardened "appliances?" This wouldn't have to be sold as hardware, it could just be an install. The machine would only have the function of storing and verifying passwords, and secure communication with authorized clients. All apis could use fixed-length fields. Passwords themselves could be stored using a modified salting technique using a white-box version of block cipher. This would make it much harder for attackers to crack the password database. The block cipher used for the modified salt could also be implemented by separate hardware, which would make it much harder to crack the password database.
- eli 14y agoThat seems like it would be just as much work (and just as prone to errors) as building it right in the first place.
- stcredzero 14y agoNah, you just a) have to make the call to an authentication function twice (first call sends the old hash hashed again into to the new system, then if that doesn't auth, call the old system), b) set up a migration that inserts the old password hashes into the new system. The new system hashes that data for you.
- lawnchair_larry 14y agoI think if you care enough about password security to know these appliances exist, you already know how to use a proper password storage scheme. The ones that we are seeing dumped were not even trying.
- derefr 14y agoWhat the parent is talking about is basically a solution to the http://en.wikipedia.org/wiki/Principal%E2%80%93agent_problem http://en.wikipedia.org/wiki/Principal%E2%80%93agent_problem. I don't think these password compromises were likely failures of management to say "let's build a secure system"; they were failures of the engineers told to "build a secure system" to know and care enough about building secure systems to learn about things like bcrypt/scrypt in the first place. The solution to this, of course, is to make password security into its own industry, with its own principals who are incentivized to understand every facet of secure systems. This would resolve as the parent explains--third-party vendors selling these companies multi-million-dollar "password appliances" with installation, support contracts, and all of that brouhaha--and then bringing in their support engineers to teach the company's own people how to securely call into the appliance.
- stcredzero 14y agoI don't think these password compromises were likely failures of management to say "let's build a secure system";... The solution to this...would resolve as the parent explains--third-party vendors selling these companies multi-million-dollar "password appliances" with installation, support contracts, and all of that brouhaha--and then bringing in their support engineers to teach the company's own people how to securely call into the appliance. Screw that. Just use a specific API in BSON structured with fixed-length fields to make the call. Build the appliance as proprietary software to install on top of an existing secure Linux distro. Sell to small sites for $1000 a pop or so, with different licensing for virtual server and cloud hosting companies. If Big Co. needs serious bandwidth, then they can do a project. Hardware component: that we'd need VC funding for. Hardware is just harder.
- diminoten 14y agoIs this newfound outpouring of confirmed hacks a result of the market becoming more blasé about leaked passwords, or is this just a statistical anomale?
- Mz 14y agoEclipse? Transit of Venus?* * (I know, I know: Wrong crowd. But take it as a tongue in cheek way of saying that it could be a "trend" with another explanation than either of the two you posit.)
- diminoten 14y agoThat's fair, I just wonder if there's some valid research worth doing here to figure out what's going on. Hacks aren't exactly going down, after all, and if we knew at least one of the causes that we don't already know about now, security might be slightly easier.
- Mz 14y agoIf you are curious about what is behind the trend, you could start a file collecting stories and see if you can spot any similarities, then ask around or whatever (I am not a hacker, so not sure what the next research step would be). That is the kind of thing I do when something piques my curiosity and I want it answered enough to satisfy my curiosity but don't care if it is answered well enough to "prove" anything to anyone else.
- joenathan 14y agoI'm not going to trust these companies again, I closed my accounts with last.fm and linkedin, you get one shot with my data.
- 5549900 14y agoIs it safe to let websites store personal information for you. Why not store the information on your own storage media that you control with your own hands? How long before Facebook is hacked? Would they even tell us about it when it happens? The websites have not proven they can safeguard personal information. Why should we keep giving it to them?
- toyg 14y agoAny info on how these passwords were hashed? MD5, SHA*, salted, unsalted...?
- jleader 14y agoThe news articles I've read said SHA-1 for LinkedIn, and MD5 for eHarmony, though I can't find the references right now.
- kibwen 14y agoPerhaps users would be better served by salting their passwords manually before signing up for any web services. If your usual throwaway password is "Passw0rd1", try "eharmonyPassw0rd1" for your eHarmony account, and "linkedinPassw0rd1" for your LinkedIn account. At this point, I can't even tell if this is sarcasm.
- mjschultz 14y agoIt might help, but I think the cracking tools would simply get an update that tries `password` and `<salt>password` (and even `password<salt>`). As the salt is guessable (as it is in your examples) it just turns into a cat-and-mouse game that the crackers win every time (since for every one of you there are probably 2 or more of them).
- AdamGibbins 14y agoOne of the primary ideas behind salts is to render pre-generated rainbow tables useless. Using a salt like the OP mentioned meets this need. Although I'm unsure to how useful and widely used pre-generated rainbow tables are with modern computing.
- mjschultz 14y agoWell, in the eHarmony case we're talking about MD5 hashes, so even if you self-salt the password but still choose a weak password a good password cracker will find the password fairly quickly. As an example, yesterday user rorrr posted this comment: https://news.ycombinator.com/item?id=4076840 https://news.ycombinator.com/item?id=4076840. > > MD5, SHA-1, SHA-256, SHA-512, et al, are not "password hashes." By all means use them for message authentication and integrity checking, but not for password authentication. > Bullshit. MD5 is just fine, as long as you use the salt. Here, hack this: MD5(password + salt) = "b520542710812f347432232b2a1fba83" salt = "MD5 rules" Self chosen salt, unknown password, known MD5 hashing method. Fire up a password cracker and feed it in a decent dictionary, and you get the password = "Spiderpig1". $ echo -n "Spiderpig1MD5 rules" | md5sum b520542710812f347432232b2a1fba83 - No rainbow table needed.