Issue
On the GitHub site there is a link...
https://help.github.com/articles/generating-ssh-keys
If you have decided not to use the recommended HTTPS method, we can use SSH keys to establish a secure connection between your computer and GitHub. The steps below will walk you through generating an SSH key and then adding the public key to your GitHub account.
Why is HTTPS the recommended method? Is there some sort of security flaw in the SSH method or is it slower? I created an SSH key, so would that mitigate any security concerns?
Solution
GitHub have changed their recommendation several times (example).
It appears that they currently recommend HTTPS because it is the easiest to set up on the widest range of networks and platforms, and by users who are new to all this.
There is no inherent flaw in SSH (if there was they would disable it) -- in the links below, you will see that they still provide details about SSH connections too:
HTTPS is less likely to be blocked by a firewall.
The
https://
clone URLs are available on all repositories, regardless of visibility.https://
clone URLs work even if you are behind a firewall or proxy.An HTTPS connection allows
credential.helper
to cache your password.https://docs.github.com/en/get-started/quickstart/set-up-git#connecting-over-https-recommended
If you clone with HTTPS, you can cache your GitHub credentials in Git using a credential helper. For more information, see "Cloning with HTTPS urls" and "Caching your GitHub credentials in Git."
Answered By - k107 Answer Checked By - Dawn Plyler (WPSolving Volunteer)