3

I just noticed that the GitHub Help is recommending HTTPS over SSH URLs

Why is this? GitHub originally recommended using SSH but they now recommend HTTPS to access and update repositories?

Robin Green
  • 32,079
  • 16
  • 104
  • 187
Alvaro Silvino
  • 9,441
  • 12
  • 52
  • 80
  • Maybe GitHub can tell you? I'm unclear of any clear advantage of HTTPS with SSH cloning right off the bat, save for the simpler approach it gives you when you want to manage more than a handful of repositories without private keys to any of them. – Makoto Feb 19 '16 at 19:01
  • 3
    https://gist.github.com/grawity/4392747 – Jonathan.Brink Feb 19 '16 at 19:03
  • @Jonathan.Brink it's very interesting information! thanks – Alvaro Silvino Feb 19 '16 at 19:53
  • @Jonathan.Brink's link provides a more thorough helpful comparison than the [GitHub Help page](https://help.github.com/articles/which-remote-url-should-i-use/). – Steven C. Howell Aug 11 '16 at 13:29
  • 1
    Possible duplicate of [Why does GitHub recommend HTTPS over SSH?](http://stackoverflow.com/questions/11041729/why-does-github-recommend-https-over-ssh) – Hugo Mar 31 '17 at 09:24

1 Answers1

5

Based on the link provided by @Jonathan.Brink, the main advantages motivating GitHub's recommendation of HTTPS over SSH URLs is that

  1. it typically works in places where SSH and plain-Git protocols get blocked (and can sometimes be faster)
  2. it allows for two-factor authentication using a personal access token
  3. it will always verify the server (though this may not be as secure as one would hope)
Steven C. Howell
  • 16,902
  • 15
  • 72
  • 97