Menu
A colleague of mine has a remote git repo that I wanted to clone and he provided a url of [email protected]:443/repo.git. ssh is listing on port 443 in this case.
I tried to clone by doing git clone [email protected]:443/repo.git but the operation times out. I had thought git defaults to ssh as its protocol and I'm not sure why this does not work.
If I explicitly specify ssh in the url like git clone ssh://[email protected]:443/repo.git it works just as normal.
Is that expected git behavior? Why does the first url not work but the second one does?
587
Git will need a ssh key only if you are using ssh protocol - there doesn't exist such a thing as anonymous ssh, ssh needs a key (an account) to work. If you use git or https protocol, no ssh key is needed.
The SSH Protocol Probably the most common transport protocol for Git is SSH. This is because SSH access to servers is already set up in most places — and if it isn't, it's easy to do. SSH is also the only network-based protocol that you can easily read from and write to.
The difference is in the protocol used, as you probably guessed. Assuming you don't much care about the technical details between HTTPS and ssh, ssh has the advantage that you can use public key authentication, while you must use a username and password with HTTPS.
The default on both GitHub.com (the website) and in GitHub CLI is using the HTTPS protocol for git operations. This default was chosen for interoperability and ease of use: Git users who are behind firewalls find that traffic to port 443 (HTTPS) is more often allowed than traffic to port 22 (SSH).
Yeah. The "default" clone syntax is scp-like. scp URLs look like "user@host:path". Note the colon; if you use [email protected]:443/repo.git, Git thinks you're trying to clone a path 443/repo.git from [email protected]. If you need to specify a port, you have to use the ssh-style syntax (as you ended up doing).
125
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
