RetroSearch Browse

Sun Aug 21 15:12:00 CEST 2005 · http://mail.python.org/pipermail/python-dev/2005-August/055526.html

It turns out that svn+ssh with a single account has limitations:
you can only set the tunnel user when you are using a restricted
key. In PEP 347, the plan is that the current SF project admins
get shell access to the pythondev account, which just has been
created.

To resolve this, project admins need two different SSH keys:
one for accessing the shell, and one for regular commit activities.

I would suggest that the default key is used for regular commits,
and a separate key is created for shell access. I described this
a bit in the PEP, essentially, in .ssh/config, I have

Host pythondev
  Hostname dinsdale.python.org
  User pythondev
  IdentityFile ~/.ssh/pythondev

So when I do "ssh pythondev", I get the shell account; when I do
"svn co svn+ssh://pythondev@svn.python.org/python/trunk/Modules",
I use my default identity, which gets tunneled as "Martin v. Loewis".

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2005-August/055526.html below:

[Python-Dev] Admin access using svn+ssh