On Thu, Jul 21, 2011 at 10:51 AM, Nico Kadel-Garcia <nkadel_at_gmail.com> wrote:
> Stop *RIGHT* there. Go grab the Subverson 1.6.x from the RHEL updates.
> Do not pass go, do not collect $200 until you do this sitewide. There
> are significant security and performance improvements, well worth the
> update pain.
Okay, we plan to do that asap, but it will take at least a little
time. In the meantime, there's no reason to believe that's causing my
problem though, right?
> That said, putting "suid" bits on svnserve is just begging for
> confusing pain in a configuration that no one has been using. Can you
> not use the svn+ssh shared account access, with SSH keys restricted to
> svnserve tunnel access, as documented in the Subversion Red Book?
That's what we're doing but the repository is owned by a separate user
as an additional security measure so that if someone somehow gains
shell access to the shared account, they won't be able to delete the
repository or anything like that. Do you think there's anyway to make
it work this way?
Thanks for the help.
Received on 2011-07-21 17:06:05 CEST