Git over HTTPS or SSH

Posted on

I love SSH keys

But they are only available when using Git over SSH(duh!).

Nowadays HTTPS is more popular, according to:

https://gist.github.com/grawity/4392747

That is because:

  • HTTPS will always verify the server automatically, using certificate authorities.
  • HTTPS works practically everywhere, even in places which block SSH and plain-Git protocols. In some cases, it can even be a little faster than SSH, especially over high-latency connections.
  • Support two-factor authentication.

Yeah, these are really good points.

But HTTPS is not developer friendly

Reason:

  • HTTPS uses password authentication for pushing, and still allows anonymous pull.

Look at this carefully…

I’m not sold

I’d love to be able to assign a key and have everything automated from commandline without user interaction. So it seemed I’ll have to wave HTTPS goodbye. At least for now.