4 ms·
You must understand that the hard part is not this, it's setting up SSH keys and authenticating for someone who a) Hasn't set up an SSH key before b) Hasn't us
by stnmtn 5y ago
You must understand that the hard part is not this, it's setting up SSH keys and authenticating for someone who
a) Hasn't set up an SSH key before
b) Hasn't used github before
It's more of a hassle now than it was 5 years ago
- nemothekid 5y ago>It's more of a hassle now than it was 5 years ago I've been authenticating with Github with SSH for 10 years - as in the creation date for my SSH key on Github is 10 years old. The process is exactly the same.
- MattGaiser 5y agoI think his point is that SSH keys are the hassle over just entering a password.
- tialaramex 5y agoThis seems wrong. Your public keys are.. public, whereas the password is secret. So you can keep those public keys on a PostIt note, on your home page, a text file pinned to your desktop, send them by email, whatever. Now I understand if your password everywhere is just pass1234 that's easier but, trouble is that means you don't have any actual security. People whose password isn't obvious are clearly better off with keys.
- MattGaiser 5y ago> So you can keep those public keys on a PostIt note, on your home page, a text file pinned to your desktop, send them by email, whatever. Everywhere I have worked that has been done with passwords so that probably illustrates many of the differences too. One job had required password changes every 90 days so we kept them on the Wiki. For many, passwords are just a required annoyance.