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

Re: bad access methods (was: 100% repeatable repo wedging)

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-03-04 22:39:02 CET

Jarod Wilson wrote:

> Which is one of the primary reasons why I do NOT want to use it. I WANT
> to have unique logins, both for security reasons and so we know exactly
> who checked in what. And there's no transport-layer encryption that way.

You are confusing "access the repository files" (server) and "accessing the
repository" (client), which are slightly different things. The first is what
user actually accesses the files on disk, whereas the second is what Author is
set to when changes are committed. These are not necessarily the same thing.

There is a patch in TRUNK which changes svnserve slightly to permit it to run as
a single user, yet use the authenticated ssh username for the Author for
purposes of committing. The developer uses:

        $ svn co svn+ssh://svn@host/repo

and you get ssh authentication and encryption, yet the repository files are
always accessed by a single user. This feature won't be available until 1.1.0
however (unless you apply the patch yourself). See this thread here:

        http://www.contactor.se/~dast/svn/archive-2004-02/0220.shtml

John

p.s. FWIW, I am planning on running with this scheme installed now, rather than
waiting for 1.1.0 to come out. I'm not recommending that... ;~)

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 4 22:37:51 2004

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