Both HTTPS and SSH are communication protocols.So, there are two popular cryptographic network protocols to use when cloning, pushing and pulling changes between GitHub repositories and your computer. As a result, many git servers, such as Github, Bitbuckets, and GitLab, use those two popular cryptographic network protocols. However, ssh and HTTPS are secure protocols. Git uses several protocols for client-server communication : Git Client) to git private repositories in a secure way so that no hacker can intercept those data.
But if you have private repositories and many developers are working on that repositories then it is necessary to transfer data between client(developer) computer(ie. For public repositories, even data send from server to client and vice versa with HTTP does not have much impact. In a git, there may be private and public repositories. So even if hackers intercept those encrypted data then that makes no sense to him since it is in encrypted form.Īs a result, many secure protocols such as HTTPS, ftps, sftp, ssh, and SSL/TLS were created. But if you want to transfer secure and sensitive data then we have to encrypt it. It can be no problem if you just use it for browsing a regular website since there does not involve any secure data. As a result, those data are vulnerable, and hackers can act as a man in the middle, intercepting all requests and responses. Anything sent from the client and received by the server via a public network (the internet) in plain text format. In standard HTTP, all information sent from client to server and vice versa is sent in plain text. In this article, I will go over the concepts and practical applications of those protocols in git.įor transferring data from client to server, protocols such as HTTP, HTTPS, ssh, FTP, sFTP, FTPs, and others have been developed. What is the difference between HTTPS and SSH in git? This is the question that every newbie has when they first start using git and GitHub.