You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Brian A. Seklecki" <la...@spiritual-machines.org> on 2007/02/22 16:31:28 UTC

--username not honored with svn+ssh:// transport

For some reason, only the current effective UID is honored ($USER) when
svn(1) sub-exec's ssh(1).

This is really inconvienent in light of the fact that "propset mode" 
refuses to work on a lot of platforms.

So you end up "sudo -H svn [...]"'ing a lot of commands to work around 
permissions problems on working copies and ./.svn/*; which has the 
side-effect of breaking a lot of automated authenticaiton (ssh-agent, 
etc.)

Shouldn't the "remote ssh-user" be recorded/cached in authentication 
tokens?

Another possibility is supporting the 'username@' in the 
svn+ssh://username[:...]@ufqdn/path

Or, just make "--username=" get passed to ssh(1) "-u".

l8*
 	-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
 	       http://www.spiritual-machines.org/

"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: --username not honored with svn+ssh:// transport

Posted by Duncan Murdoch <su...@murdoch-sutherland.com>.
On 2/22/2007 11:31 AM, Brian A. Seklecki wrote:
> For some reason, only the current effective UID is honored ($USER) when
> svn(1) sub-exec's ssh(1).
> 
> This is really inconvienent in light of the fact that "propset mode" 
> refuses to work on a lot of platforms.
> 
> So you end up "sudo -H svn [...]"'ing a lot of commands to work around 
> permissions problems on working copies and ./.svn/*; which has the 
> side-effect of breaking a lot of automated authenticaiton (ssh-agent, 
> etc.)
> 
> Shouldn't the "remote ssh-user" be recorded/cached in authentication 
> tokens?
> 
> Another possibility is supporting the 'username@' in the 
> svn+ssh://username[:...]@ufqdn/path
> 
> Or, just make "--username=" get passed to ssh(1) "-u".

I don't know the mechanism used to communicate this to ssh, but

svn+ssh://dmurdoch@my.domain/usr/home/dmurdoch/svnroot

works fine for me, while logged on as murdoch.  No sudo needed.  (This 
is running the Windows version of svn in Cygwin, not the Cygwin one.)

Duncan Murdoch


> 
> l8*
>  	-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
>  	       http://www.spiritual-machines.org/
> 
> "...from back in the heady days when "helpdesk" meant nothing, "diskquota"
> meant everything, and lives could be bought and sold for a couple of pages
> of laser printout - and frequently were."
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org