There’s a reason Github has it default and even recommends it-it works well and is easy to understand. If you’re just looking for an easy experience, HTTPS is secure as long as your password is secure. It also works better with 2FA, which most high-security Github accounts should likely be using. The question is, should you bother with it? If you’re experienced with a command line, it’s not too hard to just use keys, and most people will anyway simply because it’s easier to configure once and never enter a password again. RELATED: What is SSH Agent Forwarding and How Do You Use It? What Should You Use? The remote server acts as the middle man, unaware of your SSH key. SSH keys can also be chained together using SSH agent forwarding, which allows you to connect to a remote server, and then use the SSH key on your client machine to authenticate. While this may not be true for all Git services, it’s a nice plus for the big one: Host
SSH can even be tunnelled over HTTPS when accessing Github, using the hostname in your SSH config.
#Git add remote ssh how to
RELATED: How to Use a Different Private SSH Key for Git Shell Commands
Managing multiple keys per computer isn’t trivial, but it’s not too hard to set up by configuring your SSH host file and Git remotes. Im going to assume that youve already set up the SSH link between your computer and your GitHub profile (the instructions for how to do this are in 4).Setting up your Github account to use your SSH key only requires a few commands and clicks in their settings.SSH has plenty of downsides, but they can be mitigated if you know what you’re doing:
0 kommentar(er)
