On Tue, 2003-08-19 at 12:00, Ben Collins-Sussman wrote:
> Ask Karl about how often this happens in CVS repositories. Answer:
> ALL the time. When three cvs users all start modifying repository RCS
> files, the most *common* problems is messed up permissions and/or
> umasks.
CVS bashes your umask to 002 by default, trading off security against
convenience. We don't do that, so (at the moment) we're really
inconvenient. And I don't think we ought to start doing that, both
because it's a security hole and because it's especially impolite to
bash global process state in a library.
I think the right answer is for libsvn_fs to set the permissions of
newly created logfiles to match the permissions of the repository
itself, as defined by some reference file or the db directory or
whatever. This solution is difficult because it requires getting
Sleepycat to add support to Berkeley DB for doing that.
(You can still have a problem in CVS. On a machine with System V group
ownership semantics, with users who have different primary groups, you
have to make sure the repository is g+s or else new files won't be
writable by other users. But if you have BSD group ownership semantics,
or you have users all in the same primary group, or you have a g+s
repository root, you won't have an issue.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 22 19:16:18 2003