unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Why is the default user group "users"? and: rights and access to /var/mail
Date: Thu, 05 Apr 2018 23:43:33 -0700	[thread overview]
Message-ID: <877epkbzsa.fsf@gmail.com> (raw)
In-Reply-To: <20180402101017.3dy3g2wt6cg6u226@abyayala> (Nils Gillmann's message of "Mon, 2 Apr 2018 10:10:17 +0000")

[-- Attachment #1: Type: text/plain, Size: 2135 bytes --]

Nils Gillmann <ng0@n0.is> writes:

> 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?

Does the opensmtpd-service allow a user to customize in their
<operating-system> declaration the permissions it will use for
/var/mail?  If it does, then you should be able to specify precisely the
permissions you want on /var/mail.

> 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.

In defense of the current default, my understanding is that in shared
systems, it is not uncommon to put users in a single group (e.g.,
users).  I suppose the intent might be to make it easier for the users
to collaborate in such shared systems.  So, I didn't find this behavior
very surprising.  However, if you want to change the user/group
structure, you ought to be able to do so.  I believe you can do that by
customizing the "users" and "groups" fields of your <operating-system>
declaration (see: (guix) operating-system Reference).  You even should
to be able to remove the "users" group entirely if you don't want it.

Hope that helps!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      parent reply	other threads:[~2018-04-06  6:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 10:10 Why is the default user group "users"? and: rights and access to /var/mail Nils Gillmann
2018-04-02 11:25 ` Nils Gillmann
2018-04-06  6:43 ` Chris Marusich [this message]

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=877epkbzsa.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --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).