3 ms·
> if you only use strong password or pubkey Don't use passwords. Disable passwords. It's tempting to say "Oh we'll require 20 character long random strings, it
by tialaramex 7y ago
> if you only use strong password or pubkey
Don't use passwords. Disable passwords. It's tempting to say "Oh we'll require 20 character long random strings, it'll be fine". If you've dotted every I and crossed every T that would work, but such passwords aren't memorable so they're no better than a private key - you'll need to store them somewhere and make sure to generate them properly, you might as well use keys.
More often something will go wrong. Maybe it will be a local policy failure. "Oh I didn't realise devops needed those goofy passwords too, I thought that was just the backend team - we've been setting them all to pass1234, should I change them or is it too late now?". Maybe it will be in the password checking code, as it has happened way too often already on a broad spectrum of operating systems. Just use pubkey auth everywhere all the time.
- segfaultbuserr 7y agoWhen I setup a new server or a temporary account, my usual workflow would be simply generate a new random password locally from my password manager, before considering proper authentication. A few routers at my home with public Internet access are still password-only, and I don't see a big problem. But I have to agree with you, the suggestion "use strong password" itself is prone to failures, thus bad, and should be avoided.