On Thu, Jul 21, 2011 at 2:13 PM, Nico Kadel-Garcia wrote:
> Don't give the shared "svn" user a valid shell If an administrator
> needs to run operations as that user, to manipulate config files or
> create new repositories, they can do "sudo -s -H -u svn" to get a
> valid shell as the administ
On Thu, Jul 21, 2011 at 11:16 AM, Konstantin Kolinko
wrote:
> The scripts have execute permissions for those other users?
Yes.
> Maybe svn cannot find bash to execute those scripts? Consider what
> happens when you run with empty PATH. One known example is the tasks
> run by cron.
The same scrip
On Thu, Jul 21, 2011 at 11:01 AM, Daniel Shahaf wrote:
> ls -ald $REPOS_DIR $REPOS_DIR/hooks/ $REPOS_DIR/hooks/pre-commit
$ ls -ald repos/testrepo repos/testrepo/hooks/ repos/testrepo/hooks/pre-commit
drwxrwxrwx 7 svnuser svnuser 4096 Jul 20 13:03 repos/testrepo
drwxrwxrwx 2 svnuser svnuser 4096
On Thu, Jul 21, 2011 at 10:51 AM, Nico Kadel-Garcia 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 have a rather unique setup to meet certain requirements and as a
result I can't get any hooks to work (even empty ones or ones that
just exit with a zero return code).
In short, we have a repository owned by one user that is accessed by
tunneling over ssh to other user accounts. To get around
