News for hackers. Stuff that matters.
Re:LastPass Security Notice by dragontamer on Monday June 15, 2015 @05:14PM (#9722181)
If you wanted security, you'd use a SHA256 hash of a master-password + domain name.

http://angel.net/~nic/passwdlet.html

Storage is unnecessary. LastPass, 1Password... every one of them has centralized storage. No one needs a central server, but a central server is the only way a "service" can sell itself.

Re:LastPass Security Notice by StavrosK on Monday June 15, 2015 @05:38PM (#9722290)
There are multiple problems with this approach. SHA is way too fast, some site is always going to have Auth requirements that won't be the same as the ones you have set (one service wants mandatory special characters, one wants mandatory alphanumeric only), and, most importantly, you can't change the passwords unless you change the master password and remember which you used where.
Re:LastPass Security Notice by dragontamer on Monday June 15, 2015 @07:01PM (#9722734)
Fair point. But proper key strengthening is a well-known solution to this well-known problem. The general methodology of using password-safe hash + master password + domain name is useful.

As you note, SHA isn't appropriate for this purpose. PBKDF2-strenghtened SHA, SCrypt, BCrypt and other functions should be used.

Re:LastPass Security Notice by StavrosK on Monday June 15, 2015 @07:06PM (#9722748)
I agree, I wish browsers performed some key strengthening built in.
Re:LastPass Security Notice by andrewaylett on Monday June 15, 2015 @05:40PM (#9722298)
How do you generate a different password after that one's been found to be stored in plaintext and the admin resets all of the passwords?

Or, and more to the point, having generated a different password how do you remember which sites need a V1 password and which need V2?

When sites introduce silly rules around password structure, how do you make sure your passwords conform?

And even if you could guarantee you'll never hit any of these issues, shouldn't you be using a key-derivation function, rather than a hash?

I entrust my passwords to KeePass, as I trust its authors to have more of a clue than me and it lets me store arbitrary data rather than restricting me to a specific class of generated password. That file can then be replicated to enough of my devices that it's available when I need it, without a third-party having enough access to the data to be able to issue even the kind of security alert we see here.

Re:LastPass Security Notice by dragontamer on Monday June 15, 2015 @05:48PM (#9722330)
> Or, and more to the point, having generated a different password how do you remember which sites need a V1 password and which need V2?

> When sites introduce silly rules around password structure, how do you make sure your passwords conform?

Store _THESE_ rules in a central database. Not the passwords. Those rules can be public at no cost to security to the end user.

But LastPass, KeePass, OnePass and all sorts of Password generators store the actual friggen password, instead of salts or public information (like "5th password on gmail")

Re:LastPass Security Notice by tiglionabbit on Monday June 15, 2015 @05:19PM (#9722210)
I like this idea. I think I'll try this out for all those random dumb websites that want passwords.

You linked to the old version btw. Updated version is here: http://angel.net/~nic/passwdlet.domain.html

Re:LastPass Security Notice by gregmac on Monday June 15, 2015 @05:44PM (#9722321)
I use LastPass to also store the username I used, which is handy given that:

1. Some sites use email, others use username (and sometimes your usual username is taken), and a handful of sites assign you something (eg: with an old VoIP provider I used to use, I had to log in with my customer number instead of a username)

2. I use a unique email address on every site, in the form "[email protected]", though occasionally I have "[email protected]" (eg: I use "amazon@" because I my account works with both amazon.ca and amazon.com)

LastPass remembers all this crap for me, and it also lets me keep other notes, password history, etc, as well as being quite convenient.

Re:LastPass Security Notice by dchest on Monday June 15, 2015 @05:44PM (#9722317)
Re:LastPass Security Notice by ecdavis on Monday June 15, 2015 @05:50PM (#9722347)
I've considered this before. It's a nice idea, but it suffers due to the arbitrary length and complexity requirements that many sites place on passwords.
Re:LastPass Security Notice by dragontamer on Monday June 15, 2015 @07:04PM (#9722743)
I've actually got a very basic solution to that.

Use lowercase hexadecimal as the "baseline" password. From there, truncate to the length requirement, and add symbols to the end to guarantee complexity requirement.

For example, "masterpass gmail.com" will md5sum to "194b52e5". If a password requires symbols, add a "!" to the end. If it requires a capitol letter, add "A" to the end. Add in the order of "number->letter->symbol". So... a site that requires numbers, capitol letters, and symbols would be:

"194b52e51A!". (The hashed password, followed by '1A!')

Re:LastPass Security Notice by AdamGibbins on Monday June 15, 2015 @07:42PM (#9722919)
That does't sound simple, because I'm not going to remember the site specific password requirements for each of the 250 logins I have within my password manager.