Ryan Schmidt <subversion-2009a_at_ryandesign.com> writes:
> On Apr 14, 2009, at 11:06, Ben Kyrlach wrote:
>
>> Multiple users connect to SVN using SVN+SSH with a common key.
>> The *nix machine hosting svnserve is using the authorized_keys file
>> in each users $HOME/.ssh to launch svnserve when connecting with
>> said key.
>>
>> Whenever a user makes a commit to the single FSFS repository there,
>> the myrepository/db/current file has its ownership changed to the
>> user. So, if I commit, the files ownership changes to
>> bkyrlach.bkyrlach. Because the repository disallows any access at
>> the “other” level, it essentially prevents any other users from
>> committing to the repository. I’ve tried using sudo and or su in
>> the authorized_keys file to run svnserve as root, but when I do
>> this I get an error stating that I need a TTY in order to perform
>> that action.
>
> You may need svnserve to be a wrapper script that sets a different
> umask, then calls the real svnserve. This section of the book should
> help:
Or, you could use svnstsw from contrib which is suid to the svn user and
uses authz, so you get the same behavior as with https.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1717311
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
- application/pgp-signature attachment: stored
Received on 2009-04-15 02:59:38 CEST