News for hackers. Stuff that matters.
Re:New NIST password guidelines: don't require character typ... by wslh on Wednesday December 14, 2016 @06:57AM (#13175344)
Yes, and I like the approach that Trezor takes [1] for 4-digit PINs where the wait time increases by power of two. Also adding 2-factor authentication increases the security even on weaker passwords.

[1] https://doc.satoshilabs.com/trezor-faq/threats.html#brute-fo...

Re:New NIST password guidelines: don't require character typ... by noxToken on Wednesday December 14, 2016 @09:33AM (#13176168)
This is ripe for abuse. Case in point:

Back in my time in the military, there was an online portal that held your service information, the ability to request leave (time off), pay, etc. It was the place to go if you needed information aside from a paystub.

It required 8 char min, two upper, two lower, two special char (from a predefined list), and passwords would expire every 30 days. The thing is, most people knew all of their service info off of the top of their head. People also weren't requesting leave very often either, so most people would have to change their password on every login from some bullshit permutation of keyboard rolling with numbers and special chars tacked onto the end.

All that being said, you only had 3 attempts before lockout. No one wanted to risk lockout, so you'd make a throwaway password and reset it if you wanted to login. If you were locked out, it was a call to a civilian contractor with a hold time of 10-30 minutes just to get a temporary password emailed to you.

One of the easiest ways to fuck with someone was to intentionally lock out their account. It was trivial to find someone's username via searching through the email global address list. Then you pull up the portal, enter their user, smash the keyboard, and cackle as you have cost that person a guaranteed 10 minutes minimum just to do something trivial like print something from their file.

Re:New NIST password guidelines: don't require character typ... by wslh on Wednesday December 14, 2016 @09:50AM (#13176320)
Trezor is an external device (like an smart card) that you have with you, not an external system that you can abuse.
Re:New NIST password guidelines: don't require character typ... by noxToken on Wednesday December 14, 2016 @10:08AM (#13176440)
I meant the wait time increase. If I don't like you (or am just a jerk in general), I'll just write a script to automatically retry 0000 after the lockout period. I'm not trying to break into your account; I'm just hassling you with a DoS attack.
Re:New NIST password guidelines: don't require character typ... by wslh on Wednesday December 14, 2016 @10:43AM (#13176776)
I understand that and it is right but in the case of having a personal device with you, this attack will be stealing a physical object.
Re:New NIST password guidelines: don't require character typ... by drfuchs on Wednesday December 14, 2016 @08:57AM (#13175930)
Unlimited doubling of wait time puts you right back to being vulnerable to DOS.
Re:New NIST password guidelines: don't require character typ... by Loggie on Wednesday December 14, 2016 @09:26AM (#13176116)
Surely DOS would only be an issue if the service literally sat there doing nothing for that period of time? Isn't the solution here just to reject all requests for that period of time doing the absolute minimum processing required?
Re:New NIST password guidelines: don't require character typ... by detaro on Wednesday December 14, 2016 @09:28AM (#13176127)
Not DOS against the entire service, against a targeted user not being able to access the server (because you just entered a wrong password often enough that the system blocks his valid log-in attempts).