4 ms·
So essentially this is a really convoluted way of concatenating username, password, and domain then running scrypt() on it, and sending that to the server as th
by Someone1234 11y ago
So essentially this is a really convoluted way of concatenating username, password, and domain then running scrypt() on it, and sending that to the server as the password instead of the raw password itself?
I actually read the Github page for this, and glanced over the C#. There's no realistic example of how this would work in practice, and I have unanswered questions. This would legitimately solve some phishing scenarios and MIGHT slightly mitigate password reuse scenarios (since they know username + domain, they now need to spend time cracking scrypt() on the password). The arguments that it helps user privacy (NSA something something) are tin foil hat wearing jibberish.
Overall: Meh. If they're serious about this, they need more than a vague proposal.
PS - And a password manager solves all of the named issues with less complexity in my opinion.
- paulgb 11y agoThere is a (somewhat) practical version of this implemented as a bookmarklet: http://www.supergenpass.com/ http://www.supergenpass.com/ I used it for years (for unimportant things) before switching to a password manager. It's technically not secure against a malicious site that sniffs for the existence of the bookmarklet window, but it's a good way to get slightly better security on sites you'd other reuse the same password for.
- capnrefsmmat 11y agoI use a much simpler version of the idea in the form of PwdHash: https://www.pwdhash.com/ https://www.pwdhash.com/ Before submitting passwords to a website, they're replaced with a hashed version which incorporates the domain, so passwords are unique to each domain. (The hash isn't anything fancy, so it could definitely be modernized with scrypt or bcrypt or whatever is fashionable.) I've used it for years and it always works well, apart from the sites that claim my password is too long. It requires no support from the website, just a simple browser extension.
- jonknee 11y agoWhy not just use a password manager?
- deleted 11y ago[deleted]
- AdmiralAsshat 11y agoWhat happens if your password is leaked? It seems to generate the same hash every time, so you would have to change the site password. And if you have to start remembering "Well my password for every site is 'pumpkin' EXCEPT for Wordpress, where my site password is 'bagel'," that list is only going to grow with time as websites inevitably get hacked. So once you've got five or so site-specific passwords, how is it any better than the password memory problem this was originally trying to solve?
- mercora 11y agoI thought about using pwgen locally with a combination of domain, username and password as a hashed seed. But like you mentioned, trying to remember how often i had to change the password (or had restrictions applied only at a particular site, which are pretty ridicules sometimes) makes this not really a worthwhile solution. Albeit this, its not completely useless. If you have specific rules how to create new passwords (a counter for example) and to circumvent specific restrictions, one could iterate through the possibilities rather quickly. One thing that's unbeatable about this solution is that no password store is needed and so none could be lost, which drove my initial thought to this.
- mapgrep 11y agoI used to use that too before I adopted a password manager. Pwdhash uses md5, which is relatively fast. According to the below, even a strong master password could be derived in less than about 30 days. https://security.stackexchange.com/questions/52355/how-secure-is-the-pwdhash-algorithm-and-system https://security.stackexchange.com/questions/52355/how-secur... On the other hand, the odds you'll be the victim of such a targeted attack are presumably pretty low. This at least gets you out of the category of "low-hanging fruit" for an attacker.
- jgrowl 11y agoI don't hate the idea, but I could never use this while so many sites still have dumb validation rules. It would drive me crazy if I had to remember what sites this didn't work with.
- murbard2 11y agoTheir generation isn't great. They should tweak the resulting password to ensure that it passes most common tests. I think I would enforce - 10 characters - at least one punctuation - at least one digit - at least one upper case - at least one lower case By coercing the password to have this form you're losing a trivial amount of entropy, but you'll pass the vast majority of password policies. Also add a nonce to the password generation (1, 2, 3, 4) so that you can change it if needed or required. No need to remember the nonce, just try a few until you can login.
- nfriedly 11y agoI don't remember where off the top of my head, but I'm pretty sure I've seen sites that had a "no punctuation in passwords" rule. I think at least one of them was a bank.
- murbard2 11y agoMakes sense, it's so their IT department can read it to you more easily over the phone.
- Zancarius 11y agoNespresso is one that immediately comes to mind as it's the most recent I've encountered besides my bank. I went to order some pods for my mum as a gift only to discover that their password restrictions were not only draconian but stupid. The moment a site prohibits punctuation (especially single quotes as they did) is the moment I suspect they're storing passwords in plain text. It's not directly related, but I'm reminded of this Hall of Shame I stumbled upon from some HN comment a few weeks ago: http://plaintextoffenders.com/ http://plaintextoffenders.com/
- 11y ago
- Gankro 11y agoPwdHash has serious usability issues: http://people.scs.carleton.ca/~paulv/papers/usenix06.pdf http://people.scs.carleton.ca/~paulv/papers/usenix06.pdf In particular, the fact that you type your password into the password field means that failing to invoke PwdHash means you either register with your raw password (making it worse than useless) or just leak your raw password with failed login attempts. The password manager model (e.g. LastPass) is clearly superior in my opinion because the user doesn't know their passwords. Largely the only way to input your password is the correct way. Also determining the password for one site provides no information for others (assuming you're random generating the passwords). For PwdHash, if you crack the password you have a lot of information for breaking all the user's other accounts (because presumably they're reusing the same base password).
- bad_user 11y agoI've been actually using a similar solution for my own passwords, having built a small utility myself: https://github.com/alexandru/parolamea https://github.com/alexandru/parolamea ; it works by doing an HMAC+SHA256 between an easily rememberable service identifier (like the domain) and the secret master password and then I'm converting that to base 64. Using SHA is of course discouraged, because compared to bcrypt the collision attack can be parallelized on top of GPUs and you can try tens of billions of combinations or more on top of commodity hardware. But here's the gist - with a good salt, the complexity of finding collisions is about 2^256. Basically without knowing the salt, you're shit out of luck, because all the PC or GPU power in the world cannot crack 2^256. You can't use rainbow tables either and there are no shortcuts discovered for SHA-256, like you've got for MD5. And then you've got things like bcrypt, an 11 years old algorithms that can't be parallelized over GPUs and that's still unbreakable. I disagree with you. This doesn't just slightly mitigate password reuse. It actually solves it. And for me it's way better than a password manager because (a) it isn't a single point of failure like LastPass, (b) you don't have to trust a proprietary binary blob like 1Password, (c) you don't run into the risk of losing access, as everything is in your head, (d) when one of your passwords is compromised, you have the incentive to change the master passwords which will trigger a change of all the passwords, everywhere and (e) best of all it's free.
- ntucker 11y agoI've been using something similar of my own making, and I've been meaning to clean it up and publish it at some point. Since I have enough side projects going that I have no idea when that will be, I'll share a couple features of mine that I think make it unique and which I think should be incorporated into the others. The general concept I stole from somewhere else -- you've got a stored list of sites and when you type your master password in a field, each site in the list then gets a "copy password" button based on the site name + master password. But this isn't quite flexible enough for general use, so I added some features: First, each site has a 'version' field which becomes just another piece of data input to the hash. This makes it so you can rotate passwords on a particular site without changing your master password: increment this number and you get a whole new password. Second, each site has a password 'scheme' which allows for disparate password requirements on different sites. The underlying generation algorithm is the same, but rather than converting the hash output to a base64 number and using it directly, the hash output is used to deterministically select characters based on the rule set. Roughly, each scheme has an arbitrary number of character "classes" that may be included (e.g. "numbers", "letters", and "symbols") and each scheme may specify a minimum number of characters from each class (a typical rule being that that min=1 for numbers and symbols). So the class-specific minimums are satisfied, then the rest of the characters are selected from all classes equally, then a few more bytes of hash are consumed to deterministically change the order of the selected chars (otherwise you'd always end up with your minimum two special characters at the front, for example, which technically weakens the password). Each site also can have a distinct password length setting. Currently I only have three or four different "schemes" defined and haven't had the need to add one in a while so they're all hardcoded, but one could easily imagine having a "password scheme editor" which lets you define new ones with a few primitive rule types. And third, each site has a "last changed" date which helps me keep on top of which site passwords haven't been rotated in a while. If you change your master password every time you need to roll one site's password, this probably isn't an issue for you, but I definitely prefer to avoid the ritual of changing passwords on every site I use at once. My impetus for all the password scheme complexity is that I found that more straightforward password generators simply don't work on all sites, and I hated having exceptions. The site where I pay my electric bill, for example, doesn't allow exclamation points in passwords, and they must be between 6 and 8 characters. Lame to be sure, but I really have no choice but to go along, so my password generator must too. All that said about my password generator, I think this is a fundamentally different approach to the problem and I think the cbcrypt approach is ultimately more interesting if we can get it incorporated into browsers. I've long thought we should expose some sort of modified SSH-agent functionality to the browser JS API so sites could do public key auth for login (with the appropriate user prompting, of course -- just allowing websites unfettered access to your SSH agent would obviously be a terrible idea).
- hinkley 11y agoI don't think that's right. There's a keypair and although the text of the article doesn't say it, I see evidence of a Challenge-Response in the source code (they have files named Challenge and ChallengeResponse).
- Taek 11y agoPassword manager still have weaknesses. For one, you are still sending the private key to the server. This may happen in plaintext, or the password may not be encrypted/protected properly server-side. And it requires you to keep a database of passwords that you need to synchronize between all of your devices. Using something like public key authentication allows you to use the same public key for every website. Your password management software and synchronization strategies are both suddenly a lot simpler. Server-side mistakes are less problematic to the end user. It removes several points of failure, and has greater flexibility against user, server, and developer mistakes.
- pmontra 11y agoThere are client side password managers. Example: keepass/keepassx.
- AstroChimpHam 11y agoOn topic: the guy who made it literally has another repo called tinhat: https://github.com/rahvee/tinhat https://github.com/rahvee/tinhat
- burrows 11y agohttps://github.com/burrows-labs/pz https://github.com/burrows-labs/pz