Thank you all for replying.
I think this solution would be the best..
I will ask for a new group.
Prasad
Marilyn Sander wrote:
> Here is how I did it on Solaris.
>
> All our vobs are owned by user vobadm, group cm. This makes
> administration easier and prevents anyone but vobadm
> from doing dastardly things. Also, the development vobs are a public
> vobs, which means you have to present the registry password
> in order to update the registry entry.
>
> For the vob with the restricted access, there is a special
> group defined for those who need acccess to it.
> That group is the "aditional group" for the vob.
> The vobadm account belongs to that group (as well as to
> cm and to other groups in our shop). Of course, when
> you create the vob as vobadm, group cm, you then have to
> use protectvob to delete the groups that shouldn't have
> access.
>
> Finally, a post-op trigger on mkelem changes ownership and
> permisions of each element as it is created. Ownership is
> changed to vobadm, group ownership is changed to the special
> group, and permissions are changed with g+w,o-rwx. This
> prevents anyone outside the group from even seeing the
> elements.
>
> --Marilyn Sander
>
> | Date: Thu, 03 Feb 2000 10:58:24 -0800
> | From: Prasad Herur <prasad@dotwireless.com>
> | To: cciug@Rational.Com
> | Subject: [cciug] How to put confidential stuff into CC
> | Hi,
> |
> | I have the task of maintaining some confidential code.
> | Only 5 engineers need to have read access to this VOB.
> |
> | All the machines are solaris boxes.
> |
> | 1> Is there a way of achieving this when these 5 engineers belong to
> | the same group as other engineers, like firing a trigger which checks
> | the user name whenever some one gets into this vob.
> |
> | 2> Can I ask my sys admin to create another user group,
> | and use protectvob to add the new group and delete the
> | general users group for this vob.
> |
> | 3> Is there some other way of restricting read access to a vob.
> |
> | Any and all comments are welcome.
> |
> | Prasad
>
> -----------------------------------------------------------------------
> Marilyn E. Sander, CM Engineer marilyn@hal.com
> Fujitsu System Technologies (408)341-5590
> Division of HAL Computer Systems, 1315 Dell Avenue, Campbell, CA 95008
> -----------------------------------------------------------------------
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Sun May 06 2001 - 00:23:01 EDT