| 1 |
On Saturday 31 May 2003 10:53, Martin Lesser wrote: |
| 2 |
> |
| 3 |
> 1. Several uid's/gid's differ from other distris (debian i.e. assigns |
| 4 |
> 31/32 for postgres, gentoo uses 70/70 for postgres but 31/31 for |
| 5 |
> squid, so having both distris on different hosts leads to really |
| 6 |
> 'funny' results if you also use a central user repository or try to |
| 7 |
> merge both passwd-files, see 3.) |
| 8 |
> |
| 9 |
> If you have a access to a running debian system look at |
| 10 |
> /usr/share/base-passwd/passwd.master |
| 11 |
|
| 12 |
IMHO applications should not care about the actual uid's gid's they have, only |
| 13 |
that they can find theirs from the passwd database. Applications that need |
| 14 |
hard uids/gids should be patched. (Of course it should be possible to ensure |
| 15 |
the existence of a particular username /groupname before the configuration |
| 16 |
step. But that is possible in current portage. |
| 17 |
|
| 18 |
> |
| 19 |
> 2. In /etc/passwd from baselayout there are several users predefined |
| 20 |
> which are really unnecessary on many systems. Why do I need a user |
| 21 |
> games? Or squid on a host which never runs a proxy or another proxy |
| 22 |
> like oops? Etc. |
| 23 |
> |
| 24 |
You are right, apps should request their own users/groups if needed. |
| 25 |
|
| 26 |
> 3. If one runs openldap for authentification and nss one don't want to |
| 27 |
> maintain two sources of uid/gid's which - if you run different |
| 28 |
> distris - may conflict in an odd way. |
| 29 |
> |
| 30 |
|
| 31 |
Normally in such a setup it makes very much sense to have system users such as |
| 32 |
root and service users (for daemons) to be still in passwd, and have only |
| 33 |
real users (uid>1000 or whatever is defined) be served by the ldap database. |
| 34 |
This makes sure that the system is still working even if the ldap server is |
| 35 |
offline. (Also put at least one acount in passwd that allows ssh logins) |
| 36 |
|
| 37 |
> IMO a clearer approach could be: |
| 38 |
> |
| 39 |
> 1. The predefined entries in /etc/passwd should be reduced to exactly 1 |
| 40 |
> entry for root, all other (system-)users could be created dynamicly |
| 41 |
> by the ebuilds without assigning a fixed uid/gid. |
| 42 |
> |
| 43 |
Almost agreed, users like nobody and others are also required in baselayout, |
| 44 |
but the idea is ok. |
| 45 |
|
| 46 |
> 2. The current ebuilds which assign _fixed_ uids/gids could be fixed so |
| 47 |
> they don't use the appropriate useradd/groupadd options any longer. |
| 48 |
|
| 49 |
They should be indeed. |
| 50 |
|
| 51 |
> I don't see any benefits of developing and/or maintaining a predefined |
| 52 |
> /etc/passwd with more than exactly one entry for root. |
| 53 |
|
| 54 |
Agreed except the need for a few more predefined users /groups (The users |
| 55 |
group is for example also required) |
| 56 |
|
| 57 |
Paul |
| 58 |
|
| 59 |
-- |
| 60 |
Paul de Vrieze |
| 61 |
Researcher |
| 62 |
Mail: pauldv@××××××.nl |
| 63 |
Homepage: http://www.devrieze.net |
Archives