Quoth Pete Kruckenberg on Sat, Jan 02, 1999:
> RedHat is a little bit different with their group management. Every user
> is in his own group, so 002 and 022 are essentially the same. There isn't
> a "users" group like BSDI has (well, not by default).
Yes, I know that. I just don't understand the reason why the
hell they did it this way. And even if 002 and 022 are
practically the same, setting umask to 022 is still a better
idea, just in case. Call me paranoid if you want. But many
people change the configuration of adduser to _not_ create
personal group for each user, and that's just one reason. There
may be others, but I don't want to know. And, of course, as Jim
Knoble said, it's not exactly the umask value root wants to have.
Groups in UNIX exist to make user management easier for the
admins. Different primary groups may have different home
directories, disk quotas, and other privileges, and secondary
groups usually give users additional privileges (for example, I'm
a member of 4 groups at work and of 7 groups at my home UNIX
box). Therefore, making groups personal does not make sence. At
least, my poor imagination can't make up any reason for that.
And it makes /etc/group grow for no apparent reason.
But exim-users is a wrong mailing list for that. RedHat-devel,
maybe?
Quoth Jim Knoble on Sat, Jan 02, 1999:
> That depends on what group ought to be able to write to /etc/aliases.
> If some group `mailadm' ought to be able to update /etc/aliases, then
> 0664 is the proper mode.
Well, that's right in this case. I just was under impression
that anyone who edits /etc/aliases must have root permissions,
because it's a very big security issue. On the other hand, there
may be people who must edit /etc/aliases, but you will not ever
thing about giving them root password.
Happy New Year,
Vadik the BSD maniac.
--
Time is an illusion. Lunchtime doubly so.
-- Ford Prefect
--
*** Exim information can be found at
http://www.exim.org/ ***
