News for hackers. Stuff that matters.
Re:300M Freely Downloadable Pwned Passwords by oelmekki on Thursday August 03, 2017 @02:31PM (#14922335)
I really would love we be done with passwords altogether. We're asking non power users to make their password unique, and then make it complicated, and then remember all of them in their head, not on a post-it. Nobody can do that, not even us who are telling them to do that. And then, we explain to them they're dumb if they didn't do that.

Currently, my way to generate a new password is this : `pwgen | md5sum`. And then, I use "lost password" everywhere (but for my mailbox, obviously), that is, the rare times my browser is not already prefilling the login form.

This makes me wonder why we don't just go with that : generate a random password for the user in registration form, allow the browser to save it. On the login form, check if fields are prefilled. If not, only display an email field and send an auth link as mail. User clicking it (once, and fast enough) is logged in.

You still have to remember your mailbox password, but that's the only one, quite akin the root password of a server.

Re:300M Freely Downloadable Pwned Passwords by Poc on Thursday August 03, 2017 @03:05PM (#14922687)
I personally use KeePass, I generate 20+ character random passwords and it save them in a encrypted file. I just wrote my email password and hide it in case I lose my file.
Re:300M Freely Downloadable Pwned Passwords by dEnigma on Friday August 04, 2017 @04:15AM (#14927185)
I also use KeePass to generate long, pseudo-random passwords. The amount of different passwords I need is far beyond what I can hold in my head, especially when they have to be secure. I got my closest family to use KeePass too, which lead to a significant reduction in lost passwords and hacked accounts.
Re:300M Freely Downloadable Pwned Passwords by ShinTakuya on Friday August 04, 2017 @04:50AM (#14927274)
Or, you know, you can just use a password manager. Using forgot password all over the place is a bad idea, a lot of sites send you a temporary password that people can find in your emails if they ever hack your emails.

Pick a really good password for your password manager and remember that. Doesn't matter too much which password manager. If you're paranoid use KeePass, otherwise I personally use LastPass.

Re:300M Freely Downloadable Pwned Passwords by oelmekki on Friday August 04, 2017 @09:06AM (#14928358)
If someone access my mailbox, they'll use lost password to access other websites :)
Re:300M Freely Downloadable Pwned Passwords by peterwwillis on Thursday August 03, 2017 @08:44PM (#14925426)
Problems: 1) email is insecure, 2) it requires two logins, 3) it's not dual factor, 4) it's more error-prone. It's less work [and more secure] to just implement Google or Facebook authentication.

In terms of generating a strong password: most browsers have password generators (which I didn't even know about until recently). They aren't all enabled by default and they don't work on all forms, and not all browsers have them. Browsers also have supported user certificates [which are more secure than passwords, sort of] for like 15 years, but nobody ever uses them. The main reason (afaik) is how shit the browser's UX for them was, in combination with a burden of complexity - and of course you can't use them on random public devices.

I think we are close to reaching an authentication nirvana. If U2F came embedded in all new computing devices, and an open method of securely synchronizing all devices and service providers was used, we could effectively skip passwords, and rely almost entirely on backup codes for the few times they were needed. A lot of laptops and phones come with fingerprint scanners now. If those scanners were used as part of a U2F solution we would have a pretty solid authentication mechanism. (fingerprints are not foolproof, but IMHO they are about as secure as a password)

Re:300M Freely Downloadable Pwned Passwords by belzebub on Thursday August 03, 2017 @02:59PM (#14922622)
Email address is stupid, we should have randomly generated proxy email addresses.
Re:300M Freely Downloadable Pwned Passwords by thephyber on Thursday August 03, 2017 @03:06PM (#14922704)
A former coworker makes liberal use of American Express disposable credit card numbers -- proxy credit card numbers that you can request to give away to less than trustworthy merchants.
Re:300M Freely Downloadable Pwned Passwords by jacobwg on Thursday August 03, 2017 @03:56PM (#14923191)
Privacy (https://privacy.com/) offers a similar service for those that want something that works with more than American Express cards or other such offerings from other card issuers.
Re:300M Freely Downloadable Pwned Passwords by phs318u on Thursday August 03, 2017 @11:13PM (#14926062)
Did not know about this! Checked it out, got really excited... and then discovered it's US only :-(
Re:300M Freely Downloadable Pwned Passwords by geostyx on Thursday August 03, 2017 @03:59PM (#14923226)
I use this all the time. It's great.
Re:300M Freely Downloadable Pwned Passwords by tatersolid on Thursday August 03, 2017 @09:48PM (#14925730)
My Citibank card has the same feature, although the number generation applet requires Flash. On a banking website. In mid-2017.
Re:300M Freely Downloadable Pwned Passwords by dabber on Thursday August 03, 2017 @11:01PM (#14926006)
Email addresses have been working fine for me. What I would love though is a way to easily alias my phone number.
Re:300M Freely Downloadable Pwned Passwords by dredmorbius on Saturday August 05, 2017 @01:19AM (#14934351)
So long as you're hashing the output, go straight to the source. And if you're going to hash, use a longer hash.

    dd if=/dev/urandom bs=2048 count=1 | od -A none -l |
        sha512sum
Or just generate a long password:

    pwgen 2048 1
Re:300M Freely Downloadable Pwned Passwords by Franciscouzo on Thursday August 03, 2017 @04:35PM (#14923600)
Just use pwgen 32 instead
Re:300M Freely Downloadable Pwned Passwords by lorenzk on Thursday August 03, 2017 @03:05PM (#14922693)
Why pipe to md5sum?
Re:300M Freely Downloadable Pwned Passwords by oelmekki on Thursday August 03, 2017 @03:20PM (#14922856)
I could just pass an option to make pwgen generate longer passwords, really, but I find amusing the idea of generating the hash of 160 urandom level generated passwords :) Now that's random! Oh, and also, it looks like a hashed password, so special troll points if a cracker find the password and think it's its hash.

(note for people who may not know pwgen : it outputs 20 lines of 8 random passwords)

Re:300M Freely Downloadable Pwned Passwords by agwa on Thursday August 03, 2017 @04:16PM (#14923403)
> (note for people who may not know pwgen : it outputs 20 lines of 8 random passwords)

Unfortunately, it only does this if STDOUT is a TTY. If it's a pipe, then it outputs a single 8 character long password. So I'm afraid you've been generating rather low entropy passwords by piping the output of pwgen through md5sum.

You can confirm this by piping pwgen through cat: pwgen | cat

Re:300M Freely Downloadable Pwned Passwords by oelmekki on Thursday August 03, 2017 @06:41PM (#14924623)
Oh, you're right. Thanks for pointing that. Damn, that was an unexpected behavior (although, I can understand how it's helpful, when you want to get a password from a script/program that executes pwgen - but then I guess an option would have been enough).
Re:300M Freely Downloadable Pwned Passwords by lathiat on Thursday August 03, 2017 @05:25PM (#14924038)
i simultaneously love and loathe programs that do this, I long for some kind of shell pipe negotiation.

Most annoying trying to use "watch" or "less" and have the color work. "watch --color juju status --color", ahh. :-)

Re:300M Freely Downloadable Pwned Passwords by agwa on Thursday August 03, 2017 @05:40PM (#14924146)
Having used isatty in some of my CLI programs to alter the behavior depending on whether STDOUT is a TTY, I see the appeal. It allows the program to do the best thing depending on how it's being invoked.

However, more recently I've grown skeptical. It leads to surprises, and if a person isn't familiar with the finer details of file descriptors, they may wonder why piping a program changes its behavior. I think this example of someone shooting himself in the foot with pwgen has convinced me never to do this again.

Re:300M Freely Downloadable Pwned Passwords by oelmekki on Thursday August 03, 2017 @07:09PM (#14924817)
Yeah, that's a hard one. Of course, there are strong arguments for "sensible defaults". But here is how it went :

First, I used pwgen to generate temporary passwords for new unix users. I read the man page at that time, probably saw the mention about different behavior regarding output capabilities and thought : "nevermind, this is not my use case". Years later, when I decided to pipe it, I thought I already knew the program, and certainly not thought : "hey, let's check the man page again to see if the behavior may be altered on a pipe". Especially since I did not think it was a big deal, I was not putting that in a codebase, I just wanted to generate a random password to upload gifs or something.

And that's the interesting thing : should I have wanted to put it in a codebase, I would have read the man page again carefully.

All of this points to one conclusion : consistent defaults for end users are more important than sensible defaults for developers. You can expect developers to pay special attention, so that's ok to alter behavior for them through flags rather than detection of what stdout is plugged in.

Re:300M Freely Downloadable Pwned Passwords by amenghra on Thursday August 03, 2017 @08:02PM (#14925217)
You can use "simpler tools", such as `head -c 20 /dev/urandom | sha1`.

If head behaved differently when piped, you would probably know about that because it's a common thing to do.

Re:300M Freely Downloadable Pwned Passwords by jwives on Thursday August 03, 2017 @04:35PM (#14923596)
md5sum is going to limit your generated passwords to 128-bits because you're limited to 32 hexadecimal digits, which are each represented by 4 bits. [a-z][A-Z][0-9] can be represented by ~6 bits, so 32 characters would allow for 190 bits of entropy.
Re:300M Freely Downloadable Pwned Passwords by YSFEJ4SWJUVU6 on Thursday August 03, 2017 @03:09PM (#14922740)
To format the password I guess? pwgen sounds like a command that might be able to do that, too, though, but I wouldn't know.

Anyway, as far as password creation goes, here's another alternative based on more standard tools:

   head -c NN /dev/urandom | base32 # or base64, or md5sum if you so prefer
Re:300M Freely Downloadable Pwned Passwords by hippich on Thursday August 03, 2017 @09:25PM (#14925625)
chrome already does that (but i still stick with keepass)