[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[newbie] ssh key setup problems

From: Alan <alan_at_ufies.org>
Date: 2004-08-06 23:53:46 CEST

Hi folks, just trying to get subversion all setup properly for my work
setup and am having a few issues that don't seem to work as they should
as described in the faq/book.

My setup:
server: svnserve running on a linux server under inetd, as user subversion,
group subversion, with repository having group write access. User 'dev'
is in group subversion. The server is called 'devserver'.

client: mac os/x using the command line svn client. The username I use
on my mac ('alan') is not one that exists on the server. The server
user is 'dev'. I have ssh keys and ssh options set up so that I can log
from my client into the server automatically by just running 'ssh
server' and be logged into the server 'devserver' as user 'dev'.

What I'd like to do is be able to run the system like I did with CVS,
simply doing 'svn ci foo.c', etc. I set $CVSROOT to
'svn+ssh://dev@devserver/' and the plain svn:// equivilant, but when I
try to login I'm still prompted for a password for username 'alan'
(my local os/x user). If I don't hit anything I'm prompted for
username and password and if I fill this in with 'dev' and that user's
password it all works fine. However, based on what I've read and seen
this *should* be possible. The username and password is being cached in
~/.subversion/auth/, but I'm still prompted every time.

I'm sure it's something obvious, but I can't see it.


Alan <alan_at_ufies.org> - http://arcterex.net
"There are only 3 real sports: bull-fighting, car racing and mountain 
climbing. All the others are mere games."                -- Hemingway
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 6 23:52:21 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.