public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arsen Arsenović" <arsen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Setting default HOME_MODE in /etc/login.defs
Date: Sun, 11 Feb 2024 14:37:59 +0100	[thread overview]
Message-ID: <86a5o76rzq.fsf@gentoo.org> (raw)
In-Reply-To: <CAGJwT=845Re0yGrwrdDKMHZt+=cFmLEcbpv5WBDatKt-adehyg@mail.gmail.com>

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


Daniel Simionato <daniel.simionato@gmail.com> writes:

> Hello,
>  I'd like to start a discussion regarding setting HOME_MODE by default in
> the /etc/login.defs file (owned by sys-apps/shadow package).
>
> Upstream keeps HOME_MODE commented:
> https://github.com/shadow-maint/shadow/blob/3e59e9613ec40c51c19c7bb5c28468e33a4529d5/etc/login.defs#L207
>
> HOME_MODE affects only useradd and newuser commands: if HOME_MODE is set,
> they will use the specified permission when creating a user home directory,
> otherwise the default UMASK will be used.
> Since the default umask is 022, keeping HOME_MODE unset will result in home
> readable home directories created by useradd, which goes against security
> best practices.
>
> The proposal is to set HOME_MODE to 0700, or at least 0750: RedHat and RH
> based distros, OpenSuse, ArchLinux all set it to 0700, Ubuntu has it at
> 0750. Debian and Gentoo are two exceptions, keeping the upstream value of
> HOME_MODE (although login.defs is changed in other ways).
>
> I previously made a PR on github where you can find more details (
> https://github.com/gentoo/gentoo/pull/35231), but as pointed in the
> comments this probably warrants some discussion beforehand.
>
> I can understand the argument against the change, which is keeping in sync
> with upstream and don't risk changing the historic default behaviour of
> tools some users might rely upon.
>
> I do believe though there's merit in providing safer and secure defaults,
> so I would like HOME_MODE to have a safe default value for Gentoo and
> Gentoo based distros.
>
> Have a nice day,
>  Daniel

+1 for 0700.  I also like the umask suggestions.
-- 
Arsen Arsenović

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

      parent reply	other threads:[~2024-02-11 13:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-10 16:57 [gentoo-dev] RFC: Setting default HOME_MODE in /etc/login.defs Daniel Simionato
2024-02-10 23:52 ` John Helmert III
2024-02-11  1:08   ` Alex Boag-Munroe
2024-02-11  2:01 ` Michael Orlitzky
2024-02-11 10:06   ` Sam James
2024-02-11 13:08     ` Michał Górny
2024-02-11  2:12 ` Eli Schwartz
2024-02-11  2:20   ` Alex Boag-Munroe
2024-02-11  8:00 ` Ulrich Mueller
2024-02-11  9:33   ` James Le Cuirot
2024-02-11 10:10 ` Sam James
2024-02-11 10:53   ` Eray Aslan
2024-02-11 11:16     ` Daniel Simionato
     [not found]   ` <0ca8c68f-11e3-4a68-a857-bfd040e6b084@iodoru.org>
2024-02-13 20:01     ` Daniel Simionato
2024-02-11 13:37 ` Arsen Arsenović [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

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

  git send-email \
    --in-reply-to=86a5o76rzq.fsf@gentoo.org \
    --to=arsen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox