R. Andrew Ohana wrote: > It's like github in that there is no shell access and everyone is under the > same username 'git'. > > If you do > > ssh -v -p 2222 g...@trac.sagemath.org > > It should display the repositories you have read and/or write access to (in > this case it should just be the sage repository), and then dump you back > into your previous shell.
Thanks for your reply! I think I understand that much. But it doesn't work for me: when I do that, ssh fails at the authentication stage, and asks me for the password of the git user, even though it also says it offered the private key (/home/marc/.ssh/sage_trac in my previous message) corresponding to the public key I pasted into the input field at http://trac.sagemath.org/prefs/sshkeys. Is the relevant authorized_keys (or whatever plays that role) updated immediately when one adds a key using the web interface, or is there a delay? Does anyone manage to connect with a public key they added that way? -- Marc -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.