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

ssh part of svn+ssh not working?

From: Greg Willits <lists_at_gregwillits.ws>
Date: Wed, 19 Mar 2008 11:59:44 -0700

OS X 10.5.2, svn 1.4.4, OpenSSH_4.5p1, OpenSSL 0.9.7l

It's either trouble with my ssh setup or my understanding of how it
should work...

After reading oodles and oodles of blogs and articles (mostly about
Linux of course), I get the impression, that I should be able to use
ssh-keygen and authorized_keys to create a collection of "users" that
are not "real" OS users which should still be able to log into the


when I attempt to use ssh via keys, I still get prompted to enter a
password (which doesn't exist). From everything I read, I am
expecting this to not happen.

Here's what I have done:

-- used ssh-keygen to create svnkey and svnkey.pub files. (For now,
no passphrases.)

-- placed the svnkey file in the client computer's user home /.ssh
folder (/Users/DUDE/.ssh/svnkey)

-- made sure owner = the user, and perms is rw for the owner only

-- on the server, there's a user named "svn" with a home folder
(where all the repos go) in which I created the .ssh/authorized_keys
file. I used cat to append the svnkey.pub and then modify that entry
with a command="" component according to all the svn docs.

-- again, perms are set so the file is owned by the svn user, and rw
for that owner only.

Now, what I believe everything I have read tells me is that I should
be able to use the svn commands like this:

    svn list svn+ssh://{server.domain}/path/to/repo

and I should not be prompted for a password because the SSH keys will
be used.

However, I always get prompted for a password. So either I'm
misunderstanding, missing some steps, or still have some perms wrong

Any suggestions?


-- gw
Received on 2008-03-19 20:01:10 CET

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.