SPIKE - SSH Key

[logwhit]

Explore more about SSH key and why it's needed.

https://docs.github.com/en/authentication/connecting-to-github-with-ssh/using-ssh-agent-forwarding https://github.com/settings/ssh/new https://jdblischak.github.io/2014-09-18-chicago/novice/git/05-sshkeys.html https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github

[logwhit]

You will need to log-into the account constantly. Using an SSH key will make it more secure but also save time. You can sign in and authenticate through the command line, rather than SSO, browser authentication, or API's (use GitHub Actions for this). Below are some items as to when you need to log into your account:

• Accessing an organization
• Using GitHub Desktop
• Authenticating from Git
• Creating a repository
• Managing collaborators

[logwhit]

As of 9/24, I will put this on Hold (leave on open) as I will not create many repos - hence the need for an SSH key (for now) is not necessary. Some troubles I have stopped at:

• I used the ed_25519 ssh key
• The ssh folder is created, however, the private keys are visible, NOT the public key.
• I need to find the public keys, but when I use my SSH key, bash states that no folder or file is assigned.

Note: I believe I created two SSH keys on accident. One being assigned to id_rsa and another id_ed25519. I will need to maybe remove one.