Re: What could go wrong with this scenario?

[Marcel van der Boom]

> A good description from the list archive:

> http://www.mail-archive.com/address@hidden/msg14117.html

From this message...

...probably need to set the set-group-id (SGID) bit on the directories
in your repository (chmod g+s) -- that usually makes newly-created files
and directories get their gid from the parent directory instead of from
the creating process on systems where that doesn't happen by default...

- usually?

If I understand correctly when I use chmod g+s on the project directory 
and I do this once the directory is created every addition and 
modification of whatever user will make sure that the file is in the 
right group and the file belongs to the creator (in the case of adding a 
new file) and preserves the ownership when committing a change.


> What is the underlying problem you are trying to fix?

See above, that is the basic idea. New files are owned by their creator 
and stay that way (this happens by default right?) others in the group 
have write rights on the file (in normal shell environment) and if 
applicable commit rights on it. Others not in the group have no rights.

This is the first of a series of activities to come to a repository 
which can hold secure files (customer owned) and free sources mixed into 
one repository. We used to have different repositories for it, but I 
have decided to plunge in and try to have them in one repository without 
 daily manual maintenance to get guarantees that information is secure.

--
Marcel van der Boom
HS-Development BV
Kwartiersedijk 14B
Fijnaart, The Netherlands
Tel. : 0168-468822
Fax. : 0168-468823
Email: address@hidden