[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: User accounts
From: |
John Darrington |
Subject: |
Re: User accounts |
Date: |
Tue, 13 May 2014 10:17:52 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Tue, May 13, 2014 at 10:11:41AM +0200, Ludovic Court??s wrote:
Before commit ab6a279, /etc/{group,passwd,shadow} were all created from
a derivation. Thus, /etc contained symlinks to those files, which were
actually in the store. Being in the store, they were all immutable and
world-readable (you can see that in the VM image released with 0.6.)
That was obviously not desirable, because then everyone can read shadow,
and because that prevents passwords from being changed.
So commit ab6a279 changed accounts to be created at ???activation
time??????i.e., when booting, or when switching to a new operating system
configuration. What happens is that the activation code checks for all
the user accounts and groups required by the ???operating-system???
declaration, and invokes ???useradd??? and ???groupadd??? for any missing
account/group.
That way, {group,passwd,shadow} are normal state files with the right
permissions, and everything works as expected. NixOS uses the same
strategy.
Does /etc/group now have a "nogroup" group? I was trying to package up GNU
cssc,
but one of its tests relies on having a group which no user is a member of.
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
- User accounts, Ludovic Courtès, 2014/05/13
- Re: User accounts,
John Darrington <=