More to the point: what prevents me from logging in using SSH
as user1 and using "--tunnel-user user2"? Seems like a security risk...
--Original Message Text---
Date: Sun, 05 Dec 2004 10:28:04 -0500
That will likely work (thanks!) but I am wondering what is going on
under the hood. It was mentioned to me that I am getting user SYSTEM
because SSHd runs under this user but I find this odd because I use a
non-SYSTEM user ID in my ssh client. Isn't the ssh server supposed to
modify my session so it is associated with the specified user ID
instead of SYSTEM?
On Sun, 5 Dec 2004 08:31:28 -0600, Ben Collins-Sussman wrote:
>Try using the --tunnel-username switch with 'svnserve'.
>On Dec 5, 2004, at 8:23 AM, Gili wrote:
>> My original message is quoted below. Any ideas?
>> On Sat, 04 Dec 2004 19:16:56 +0100, SteveKing wrote:
>>> Gili wrote:
>>>> I'm using svn+ssh:// with the following ssh cmdline:
>>>> C:\Program Files\TortoiseSVN\bin\TortoisePlink.exe -i subversion.key
>>>> username -pw password
>>>> but Subversion shows my commits as being done by user "SYSTEM".
>>>> The subversion.key has the following ssh-command associated with it:
>>>> command="/cygdrive/C/Program\Files/Subversion/bin/svnserve --tunnel
>>>> ng,no-pty ssh-rsa <key goes here>
>>> When you tunnel the svn connection over ssh, then the authentication
>>> done by ssh alone. So Subversion never even sees your authentication
>>> data. That's why the user is always SYSTEM (the user ssh is running
>>> Check the Subversion mailing list - I remember that someone had a
>>> solution to that problem by using a special tool with ssh.
>> To unsubscribe, e-mail: email@example.com
>> For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Dec 5 16:32:30 2004