Since Git 1.6.6, HTTP(S) remotes are as efficient as the git/SSH protocols. However, SSH keys are more convenient and secure for automatic authentication than HTTPS auth. As far as I know, the only way to set up automatic authentication with git over HTTPS is to store the username and password in cleartext in ~/.netrc, which for many users is not acceptable.
On Sun, Feb 7, 2016 at 11:54 AM, Kai Noda <noda...@gmail.com> wrote: > Hi Etienne, > > Thanks for your reply, it is certainly one solution employable by each Git > user. But I'm suggesting to change the default behavior for everyone, > believing there are zero cons for it. > > // If only I could send a patch w/o CLA signed by my employer's lawyer! > > Thanks, > Kai > > 野田 開 <noda...@gmail.com> > > 2016-02-08 2:20 GMT+08:00 Etienne Champetier <champetier.etie...@gmail.com > >: > >> Hi, >> >> Le 7 févr. 2016 7:06 PM, "Kai Noda" <noda...@gmail.com> a écrit : >> > >> > Hi Mono developers, >> > >> > Could you change .gitmodule so that the sub-modules are fetched with >> HTTPS rather than the git: protocol? I believe the former has a higher >> chance to pass through firewalls than the latter. >> >> See http://stackoverflow.com/a/11383587 >> >> > >> > Thanks in advance, >> > Kai >> > >> > 野田 開 <noda...@gmail.com> >> > >> > _______________________________________________ >> > Mono-devel-list mailing list >> > Mono-devel-list@lists.ximian.com >> > http://lists.ximian.com/mailman/listinfo/mono-devel-list >> > >> > > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list