2 ms·
> Let me use a password if I want, these security requirements are becoming increasing absurd - I could realistically see people just checking out of services i
by lmm 5y ago
> Let me use a password if I want, these security requirements are becoming increasing absurd - I could realistically see people just checking out of services if these invasive procedures continue. Just kidding, a lad can dream. Yeah it's not rocket surgery to add the ssh key and then clone it to your different machines but if you have strict sprint deadline or something and you haven't pulled from your repo in a day and suddenly you can't run your workflow, then that's really pretty annoying to have to run the context switch and do some random bullshit to appease your vendor's obnoxious requirements. If Millenials ever learn software engineering en-masse maybe they would decry this lack of consent in daily software engineering operations. (Haha jk... not really, but I'm a Millenial so it's ok for me to say this)
Passwords are just not viable for public-facing services any more. If they let people use passwords, those people would keep getting hacked, and the support burden (or the reputation burden if they just shrugged their shoulders) would be too high.
Frankly, between using passwords that you're forced to rotate / expire / use x special characters and y numbers, using some opaque ML system that blocks your login whenever you're travelling, and just actually using ssh keys, I know which option I prefer.