Hey! Did you see what Matthew Sachs wrote on Jul 31 ?
MS> > MS> bash# touch thefile
MS> > MS> bash# chown root.busers thefile
MS> > MS> bash# chmod 660 thefile
MS> > MS> bash# ln thefile thefile-l
MS> > MS> bash# chown root.users thefile-l
MS> > MS> bash# chmod 640 thefile-l
MS> >
MS> > Nope, this wouldn't work because once you create the link everything you
MS> > do to thefile-1 happens to thefile.
MS> >
MS> > So as soon as you... chown root.users thefile-1 ... thefile's ownership
MS> > changes as well.
MS>
MS> Hmm, could you make it owned by a dummy user who is a member of users, and
MS> have a binary that you can use to access the file which only the users
MS> group can run and is suid to the dummy user?
After reading this half a dozen times to try to figure out how you aren't
going around in circles here, I've finally decided that you are going
around in circles. :-)
This seems like an extremely untidy way of doing things. You would need
to have an entire set of utilities (cp, mv, rm, cpio, tar... etc etc) just
for accessing these files. Can you imagine it..."now which version of cp
do I have to use to copy this damn file?".
I think the best answer to this problem would be to create another group
that includes the users who are to be permitted to use this file.
Regards, Steve Youngs <[EMAIL PROTECTED]> ICQ: 34307457
------------------------------------------------------------
| __ |
| Isn't it good to know that / / __ ___ __ ____ __ |
| There _IS_ an alternative! / /__ / // _ \/ // /\ \/ / |
| /____//_//_//_/\_,_/ /_/\_\ |
------------------------------------------------------------
