From: Nils Gillmann <ng0@n0.is>
To: guix-devel@gnu.org
Subject: Why is the default user group "users"? and: rights and access to /var/mail
Date: Mon, 2 Apr 2018 10:10:17 +0000 [thread overview]
Message-ID: <20180402101017.3dy3g2wt6cg6u226@abyayala> (raw)
Hi,
can someone tell me why in gnu/system/shadow module you thought
it would be a good idea to default to "users" as a shared group
for all accounts created as normal user profiles?
Reason why I'm asking has a second question attached:
Why does our opensmtpd-service (and dovecot?) create
/var/mail world readable, owned by root:root?
I'm working on integration of mailx (package done, debugging its
runtime currently[1]), though I think my concern is not exclusive to
mailx: I want users to be able to read mailboxes inside /var/mail
by their name (/var/mail/$username) and which are set to be r+w
only for $username:$username. If you want to list the content of
the folder you would need to be part of the wheel/sudo group,
otherwise you are just able to access your mailbox with your
mailreader.
$username:$username was what I learned as good and secure usage
for user accounts. Why GuixSD uses $username:users is beyond me.
I know recently the default chmod of the user $home was changed
(last year?) so I can no longer read other users homes, but I'm
still questioning the choice.
Some explanation on this would be good.
[1] Not sure if this is something you want to see in Guix master,
as a package and as integration. If you are, I'll work it into
my Guix repo when I'm done with it.
next reply other threads:[~2018-04-02 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 10:10 Nils Gillmann [this message]
2018-04-02 11:25 ` Why is the default user group "users"? and: rights and access to /var/mail Nils Gillmann
2018-04-06 6:43 ` Chris Marusich
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=20180402101017.3dy3g2wt6cg6u226@abyayala \
--to=ng0@n0.is \
--cc=guix-devel@gnu.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).