[ On Wednesday, August 6, 2003 at 22:27:24 (-0400), [EMAIL PROTECTED] wrote: ]
> Subject: permissions on modules
>
> I only want my internal folks to view, commit, update, etc from
> client1_module. However, I want to be able to give an employee of my
> client2 access to and abilitity to commit, update, etc anything in
> client2_module.
If you really don't trust client1 and client2 to see each other's files
and to not change each other's files then you _SHOULD_ host their
repositories on separate machines, even if you use SSH and all that good
stuff.
If you're very careful, and if you use SSH and real unix accounts then
it is possible to have two completely separate repositories on the same
machine and if everyone is extremely aware of unix security practices
and diligent in following those practices, and assuming the server as a
whole is run in a secure manner, then each group of users can protect
themselves from each other.
However in the real world that pretty much boils down to forcing each
group to use a completely separate machine.
--
Greg A. Woods
+1 416 218-0098 VE3TCP RoboHack <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]> Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
