On Wednesday, February 22, 2017 at 10:05:20 AM UTC, Simon King wrote: > > Hi Dima, > > On 2017-02-21, Dima Pasechnik <[email protected] <javascript:>> wrote: > > first of all, put your (new?) ssh key to trac, and also to github, if > you > > have an account there. > > For *cloning*? Sure, I need it for pushing. But I don't think I have > ever made Sage aware of my github account (not sure if I have one). >
github accounts don't have per repo ssh keys, so even if you have one, you are safe here, Sage won't tell it to anyone. :-) It seems that 99% of active Sage devs have a git account - useful as a backup store for all your git trees you care about... > > Some firewalls prevent plain "git" protocol, in effect, you need to use > ssh > > or https > > to connect to github. > > Assuming your ssh key is there, do > > > > git clone [email protected]:sagemath/sage.git > ><http://github.com/sagemath/sage.git> > > > > this will make sure you go via ssh... > > I didn't try that, as the suggestion "use https://github... instead of > git://github..." works for me. > [email protected]:sagemath/sage.git would only have worked if you had a github account. IMHO the problem is that git automatically substitutes URLs of the form git://... with ones of the form git@... as soon as it knows that ssh authentication will work. I was hitting a similar snag some time ago, and there was a long discussion on this that I can't find ATM. Cheers, Dima > Thank you very much, > Simon > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
