Hi Toby.
Thanks for the response.
Would be I correct in saying that the only way to set this up is to use
svn+ssh access?
(The redbook seems to save that using the svnserver daemon won't accomplish
this: "When a client makes a network connection to the svnserve process
(running either as a daemon, or as a "one-off" handler), no authentication
takes place. The server process accesses the repository as whatever user
it's running as, and if the client performs a commit, the new revision has
no svn:author property at all.".
And using httpd limiting hasn't helped either.)
Thanks again.
Greg.
-----Original Message-----
From: Toby Johnson [mailto:toby@etjohnson.us]
Sent: Monday, 25 October 2004 12:56 PM
To: Greg Irvine
Cc: users@subversion.tigris.org
Subject: Re: svn 1.0.9 (rh9) + author property
Greg Irvine wrote:
>Hi all.
>
>I've just upgraded to 1.0.9 (on redhat9) and implemented as a short term
solution httpd based security for the repository for commit rights.
>
>I was expecting to now see author information in the logs (which aparantly
wasn't availabe in 1.0.1 which I had previously), but, alas, I do't.
>
>Any ideas?
>
>
Whether or not you see author information in the logs depends on whether
your Subversion server (either svnserve or Apache) is sending an
authentication challenge to your client. If you don't set up your
repository to require authentication for commits, all access will be
anonymous, and no author information will be stored. (Note that *read*
access can still be anonymous if you want).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 25 05:36:31 2004