unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Jacob First <jacob.first@member.fsf.org>
Cc: 52539@debbugs.gnu.org
Subject: bug#52539: Fwd: Comments in /etc/passwd don't get updated
Date: Wed, 22 Dec 2021 23:36:37 +0100	[thread overview]
Message-ID: <87v8zgxo5m.fsf@gnu.org> (raw)
In-Reply-To: <CAAkdc5Dup1tWTxWMVLG8AUBYju9ZtTPQVRoJ6muEAUMQy9ysZA@mail.gmail.com> (Jacob First's message of "Thu, 16 Dec 2021 07:00:59 +0000")

Hi,

Jacob First <jacob.first@member.fsf.org> skribis:

> After I apply this configuration with `guix system reconfigure', I
> expect /etc/passwd to have been updated with "New Comment" in place of
> "Old Comment". However, "Old Comment" remains.

This is on purpose, per these lines in ‘allocate-passwd’ in (gnu build
accounts):

           (real-name (if previous
                          (password-entry-real-name previous)
                          real-name))

This wasn’t a firm decision, but I think the rationale here could be
that we’d rather allow users to change their name with ‘chfn’ to
something other than what the sysadmin chose, than enforce the
sysadmin’s choice.  (Except that ‘chfn’ is currently not setuid by
default on Guix System, so the scenario above is unlikely.)

Thoughts?

Thanks,
Ludo’.




  parent reply	other threads:[~2021-12-22 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAkdc5CeSKJh8h1qvwX8fiDNS2rjXyr-4qWPEU0ZBy4+FZTDoQ@mail.gmail.com>
2021-12-16  7:00 ` bug#52539: Fwd: Comments in /etc/passwd don't get updated Jacob First
2021-12-17  4:02   ` Liliana Marie Prikler
2021-12-20 23:45     ` Jacob First
2021-12-22 22:36   ` Ludovic Courtès [this message]
2021-12-26 21:56     ` Jacob First
2021-12-31 17:32       ` Ludovic Courtès
     [not found]   ` <handler.52539.D52539.164097194432533.notifdone@debbugs.gnu.org>
2022-01-01 14:22     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8zgxo5m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=52539@debbugs.gnu.org \
    --cc=jacob.first@member.fsf.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).