put myself in group 'root'?

put myself in group 'root'?

Post by Michael B. All » Sat, 24 Feb 2001 13:06:13



Should I add myself as a member of the group 'root'? It's a home machine
so I'm not really worried about security. I just thought it might save
be from becoming root a few times. Really the problem is that I have a
separate partition called /d that has tons of junk and data and I want
to be able to access that as myself. I can chown -R it to say 'nobody'
and put myself in that grroup?

What would you do?

Thanks,
Mike

--
signature pending

 
 
 

put myself in group 'root'?

Post by Drew Roedersheim » Sat, 24 Feb 2001 13:11:06



Quote:>Should I add myself as a member of the group 'root'? It's a home machine
>so I'm not really worried about security. I just thought it might save
>be from becoming root a few times. Really the problem is that I have a
>separate partition called /d that has tons of junk and data and I want
>to be able to access that as myself. I can chown -R it to say 'nobody'
>and put myself in that grroup?

>What would you do?

>Thanks,
>Mike

>--
>signature pending

I don't know if you can add yourself to the group root or not, but I
wouldn't even if you can...  I have a separate disk that I use for
periodic backups, and I simply created a backup group in /etc/groups
and added myself to that group.  Then I chowned that mount point's
(and subdirs) group to backup and changed permissions appropriately.
This seems to be the type of behavior you're looking for.

Now, if you're wondering about being able to mount/umount a particular
partion - that's an entirely different issue.

HTH
-DR

 
 
 

put myself in group 'root'?

Post by Joseph Ovadi » Sat, 24 Feb 2001 23:12:54


Just login as root. and use that as your ID.


> >Should I add myself as a member of the group 'root'? It's a home machine
> >so I'm not really worried about security. I just thought it might save
> >be from becoming root a few times. Really the problem is that I have a
> >separate partition called /d that has tons of junk and data and I want
> >to be able to access that as myself. I can chown -R it to say 'nobody'
> >and put myself in that grroup?

> >What would you do?

> >Thanks,
> >Mike

> >--
> >signature pending

> I don't know if you can add yourself to the group root or not, but I
> wouldn't even if you can...  I have a separate disk that I use for
> periodic backups, and I simply created a backup group in /etc/groups
> and added myself to that group.  Then I chowned that mount point's
> (and subdirs) group to backup and changed permissions appropriately.
> This seems to be the type of behavior you're looking for.

> Now, if you're wondering about being able to mount/umount a particular
> partion - that's an entirely different issue.

> HTH
> -DR

 
 
 

put myself in group 'root'?

Post by Michael B. All » Mon, 26 Feb 2001 14:00:58




>>be from becoming root a few times. Really the problem is that I have a
>>separate partition called /d that has tons of junk and data and I want
>>to be able to access that as myself. I can chown -R it to say 'nobody'

>periodic backups, and I simply created a backup group in /etc/groups
>and added myself to that group.  Then I chowned that mount point's

I just made myself a member of the nobody group(already there in RH Linux)
and mount /d on boot with the grpid option like:

/dev/hda3       /d             ext2    grpid          0 0

and changed the group id of /d to nobody. The grpid option ensures
all files written get the gid of the parent directory. That should be
sufficient to satisfy the multiple personalities I have on my system :)

Thanks,
Mike

 
 
 

1. change group 0's name from 'root' to 'staff'

Hello,

I run patches Solaris 2.4 on SUN.

I run login from logdaemon-5.6 package which allows
/etc/login.access file which defines access control for users.

I also run s/key su and I have installed unix_scheme.so and these allow su
to root only for users in group 0.

I disabled root's logins via net (only from console) but the problem, when
username didn't match 'root' login searched through group file and found
'root' group.

So I disabled network logins for all people in group root, those who can su
to root. That would be 'nice' for security but it is not.

I thought group '0' can have other name (staff) but will that break
anything ?

- if i change group '0' from 'root' to 'staff', scripts and commands using
  setgid (root) and chgrp (root) wouldn't work

- if I add group 0 'staff' after group 'root' I'll have 2 groups with gid 0
  which is not complete correct... and I don't know if the second group will
  be taken with library functions...

Can anybody help ?
--


 ...and if you think I'm talking for my employer, you're wrong...

2. removeuser and sortpasswd scripts?

3. in ftp, put put *`date '+%Y%m%d'` doesn't work

4. Need help with pwd and cd../ problem

5. Intel 100Mbps card

6. Kill process through various levels script help

7. What's 'side effects' of Ksh built-ins?

8. default 'group' for root??

9. Wrong group to su 'root'??

10. Slow FTP 'gets', Fast 'puts'???

11. FTP: logging things other than 'get' and 'put'