Re:Guide to User Data Security
by mooreds on Wednesday July 06, 2016 @07:00PM
(#12046423)
How do you keep users from selecting easy passwords (or no password) for their private keys?
[ Parent
| on HN ]
Re:Guide to User Data Security
by brokenwren on Wednesday July 06, 2016 @07:10PM
(#12046465)
The libpam-cracklib does it for you. It's a PAM module that is invoked whenever the user changes their password. You can configure it to enforce various password constraints and rules.
Check out section 4.4 for a detailed overview of Cracklib.
You're answering the wrong question. They're asking about passphrase for SSH key not OS user accounts.
Adding a passphrase to your SSH private key is a best practice but not easily enforced without some manual process or command and control for sysadmin workstations.
Hardware tokens containing private keys and used via PKCS#11 are another option for providing some assurance. The token itself can require a PIN.
Re:Guide to User Data Security
by brokenwren on Wednesday July 06, 2016 @10:13PM
(#12047117)
You are correct. I missed read that question.
If you select an easy passphrase for your key, it's similar to selecting a weak password for your bank account when your bank doesn't enforce password constraints. Buyer beware.
An ideal solution would be a two-factor key encryption. That would require the two-factor key to unlock the private key. There might be something out there like that. I haven't looked though.