When you clone a repository from GitHub site, it is converted to a local file using its remote URL. The remote URL can be accessed only using SSH or HTTPS protocol, but Git does not care about the protocol. So, even if the remote URL is configured in your system using HTTP protocol, your clone will be done using SSH. The remote URL is stored in .git/info/remote configuration file. By default, this file contains a reference to the local file that stores the remote URL. When you clone a repository, it is copied to the local file system of your system as well as to the remote file system. In order to make the remote URL accessible to anyone who access your system over SSH, you will have to give the remote URL the SSH type. In order to make the remote URL accessible to anyone who access your system over HTTPS, you will have to give the remote URL the HTTPS type. In this way, you can change the type of the remote URL to make it available over any protocol, although it is not recommended for long-term usage. To change the type of the remote URL, use the following command: Git remote type -v new type>
On GitHub, the push and pull buttons are at the top-right corner of the page. If you click on the button and select the repository that you want to clone, it is copied to your local file system as well as to the remote file system.
Git remote init
If you want to keep the remote URL in your repository, use the following command: git remote set-url origin
Timeline
Published on: 04/21/2022 11:15:00 UTC
Last modified on: 08/21/2022 06:15:00 UTC
References
- https://github.com/vim/vim/commit/8b91e71441069b1dde9ac9ff9d9a829b1b4aecca
- https://huntr.dev/bounties/a4323ef8-90ea-4e1c-90e9-c778f0ecf326
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X6E457NYOIRWBJHKB7ON44UY5AVTG4HU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KVPZVE2CIE2NGCHZDMEHPBWN3LK2UQAA/
- https://security.gentoo.org/glsa/202208-32
- https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1420