News for hackers. Stuff that matters.
Re:New NIST password guidelines: don't require character typ... by Spooky23 on Wednesday December 14, 2016 @12:10AM (#13174004)
You mitigate that by putting MFA in front.
Re:New NIST password guidelines: don't require character typ... by sh_tinh_hair on Wednesday December 14, 2016 @09:13AM (#13176041)
MFA is basically another key|password. If I am not careful with my secret key and password what difference does it make that there are two of them?

No, security is tough. The better security the less useful it is. NIST got this right. Do what you can, don't kill the user and implement security on the aaa side.

Re:New NIST password guidelines: don't require character typ... by Spooky23 on Wednesday December 14, 2016 @01:18PM (#13178259)
Have you ever messed with a friend by locking out their phone?

I was specifically addressing the DoS vulnerability of locking an organization out en masse by taking advantage of account lockout or timeout policy. A list of emails and a six line script could take a whole company offline.

MFA can be used to address that by requiring pre-auth before you can enter a password.

Re:New NIST password guidelines: don't require character typ... by kbart on Wednesday December 14, 2016 @02:09AM (#13174374)
MFA is not a magic solution to all problems either. You can't expect me to give my phone number or real email address to every random site I login into.
Re:New NIST password guidelines: don't require character typ... by CiPHPerCoder on Wednesday December 14, 2016 @03:08AM (#13174555)
You don't need to do that for HOTP/TOTP though.

1. Scan a QR code.

2. You now have a secret value that can generate a deterministic pseudorandom integer securely indefinitely.

Also, SMS-based MFA should be burned to the ground.

Re:New NIST password guidelines: don't require character typ... by AstralStorm on Wednesday December 14, 2016 @04:03AM (#13174695)
Scanning a QR code by hand is easy when you don't have the phone handy. (sarcasm)

Actual OTP should allow you to print out or write down a set of codes.

Re:New NIST password guidelines: don't require character typ... by CiPHPerCoder on Wednesday December 14, 2016 @08:11AM (#13175676)
> Scanning a QR code by hand is easy when you don't have the phone handy. (sarcasm)

That's way different from "I don't want to give out my phone number".

Re:New NIST password guidelines: don't require character typ... by user5994461 on Thursday December 15, 2016 @08:34AM (#13184444)
Both are impossible when not having a phone.
Re:New NIST password guidelines: don't require character typ... by CiPHPerCoder on Thursday December 15, 2016 @11:56AM (#13186002)
It's non sequitur.

"I have a phone number but don't want to give it out" is different than "I don't have a phone".

But hey, there are 2FA devices you can use instead.

Re:New NIST password guidelines: don't require character typ... by jon-wood on Wednesday December 14, 2016 @04:31AM (#13174801)
This is why I'm a big fan of the U2F standard, which allows a device (generally a small USB/NFC device) to generate shared secrets for arbitrary services without exposing any personal information.
Re:New NIST password guidelines: don't require character typ... by Spooky23 on Wednesday December 14, 2016 @09:20AM (#13176080)
Think about this problem in context with the NIST trust level framework.

Nobody gives a shit about low trust environments... go ahead and crack my slashdot account, but higher trust stuff like mail, money, network access etc absolutely need MFA.

Re:New NIST password guidelines: don't require character typ... by kbart on Wednesday December 14, 2016 @09:33AM (#13176167)
That's my point. MFA itself is certainly a very useful security solution (for example, I wouldn't trust a bank that doesn't use it), but "MFA everywhere" is not a way to go, because I value my privacy more than some useless Internet account.
Re:New NIST password guidelines: don't require character typ... by petters on Wednesday December 14, 2016 @02:58AM (#13174528)
A security key should work.