[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best practices: managing configuration files

From: Jack Repenning <jrepenning_at_collab.net>
Date: 2003-08-14 00:49:15 CEST

At 3:02 PM -0700 8/13/03, John Locke wrote:
>So, aside from the security issues surrounding the repository, and
>as long as I get it set up correctly, does anyone see any major
>drawbacks to making /etc a working copy?

I don't think SVN is in the business of preserving file ownership.
If you do this stuff as root, they'll all come out owned by root.
Depending on your system, there might be some that would rather be
owned by some other user, like "mail" or "httpd" or something. Same
observation about group. I even wonder about the more exotic
permissions, like set-uid and sticky and such.

>I haven't dug around in the private .svn directory all that much--is
>there a security risk involved in having these files in the /etc

There's a good question. Looks like the text-base files are always
world-readable. There are a few files in /etc that should not be
world-readable. I think that's a killer for you right there.

Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 14 00:50:12 2003

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.