Setuid
From: Andy Canfield <andy.canfield_at_pimco.mobi>
 
Date: Fri, 22 Jul 2011 22:38:57 +0700 
Had what seems to be a bright idea. It is a bright idea for a Subversion 
 Take note of the user and group that Apache runs as. Call this 
 Whatever mod_dav_svn does to any repository will be done by APACHE. 
 If I set the svnserve program to be owned by APACHE, and setuid and 
 If I set the svnadmin program to be owned by APACHE, and setuid and 
 If I set the svnlook program to be owned by APACHE, and setuid and 
 So the three access paths - http:, svn:, and direct - will all operate 
 You don't want to do this to any program, such as 'svn', which relies on 
 So a post-installation setup would include:
 This idea also allows me to make the the respository itself accessable 
 If I also do this:
 How does that sound to you guys? Where are the flaws in this idea?
 Thank you very much.
  | 
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.