3 ms·
Wouldn't it also make sense to have HTTPS as default for the read-only clone URL? I for one always replace "http" with "https" before cloning.
by erikano 16y ago
Wouldn't it also make sense to have HTTPS as default for the read-only clone URL? I for one always replace "http" with "https" before cloning.
- technoweenie 16y agoNo HTTP cookies are involved, so no. For now, git will always ask for your password for https clone urls.
- pilif 16y agoI don't know. The code you are cloning is already public (exception: private repos), so it leaking to a third party is a non-issue. Additionally, a MITM changing the code on-the-fly to give you a troian horse is quite impossible to pull off as this would completely change revision IDs which you'd notice. The reason for public http cloning be there at all (as opposed to the git protocol) is restrictive firewalls (git's http support still isn't perfect), which are more likely to cooperate with http as opposed to https
- uxp 16y agoIs the git protocol unencrypted as well for read-only public repos? I should probably know the answer to that already, but I'm coming up blank. I guess a solution (for a non-issue) of pulling public repositories would be to fork the repo over the secure GitHub interface and then pull your fork over ssh...