public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Simionato <daniel.simionato@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Setting default HOME_MODE in /etc/login.defs
Date: Sun, 11 Feb 2024 12:16:27 +0100	[thread overview]
Message-ID: <CAGJwT=_5dAboO3X-2P1XUhdgYOt+FTfO-cxj+o1pR0Lo1bqTGg@mail.gmail.com> (raw)
In-Reply-To: <ZcinHuB40i5du2sd@rog.a21an.org>

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

The only previous upstream discussion I was able to find was this on the
pkg-shadow-devel:
https://marc.info/?l=pkg-shadow-devel&m=167120074926229&w=2(
(I don't think the unprivileged container limitation still applies, or at
least it doesn't on my user with a 700 /home)

I can see the argument for keeping the status quo, but I still think it's
better to err on the side of caution with default settings.
But I understand that my point of view might be skewed by personal
preference or by professional experience, so I appreciate the everyone
contributing their opinion.

I have opened a PR upstream to start discussion there
https://github.com/shadow-maint/shadow/pull/946 .

For reference, the concrete use case that put me onto this (
https://github.com/flatcar/Flatcar/issues/1353): provisioning users in
Flatcar through ignition (cloud-init like) at first boot time, even if in
the same config /etc/login.defs is changed, results in 755 home
directories. Some more comments in this PR
https://github.com/kubernetes-sigs/image-builder/pull/1400

The original PR that added HOME_MODE also refers generically to user bug
reports due to the many ways umask can be overriden:
https://github.com/shadow-maint/shadow/pull/208#issue-546914572

Thanks,
 Daniel


Il giorno dom 11 feb 2024 alle ore 11:53 Eray Aslan <eras@gentoo.org> ha
scritto:

> On Sun, Feb 11, 2024 at 10:10:13AM +0000, Sam James wrote:
> > I'm in favour, although I'd be curious as to why upstream shadow don't
> > just set it. It would be interesting to see if the discussion already
> > happened there at some point (surely it has?) and find out their
> > reasoning. (But that's not a blocker for proceeding.)
>
> I believe it is for historical reasons. Computer networks and terminals
> used to be much friendlier places.
>
> > I want to hear more opinions first though. Thanks for raising this,
> > it's been in the back of my head.
>
> Even though I do not really care either way, what problem exactly are we
> trying to solve? Better security is just too vague an argument. I can
> see the argument if we were selling to business (*cough*red hat*cough*)
> but on the other hand, an argument can also be made for keeping to the
> roots of computer networks and their naivete (keep information free and
> all that stuff). In this regard, it is telling that only debian and
> gentoo keep 022.
>
> Consider taking it upstream as someone else (ulm?) already mentioned in
> the discussion.
>
> Thanks
> --
> Eray
>
>

[-- Attachment #2: Type: text/html, Size: 3568 bytes --]

  reply	other threads:[~2024-02-11 11:16 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 [this message]
     [not found]   ` <0ca8c68f-11e3-4a68-a857-bfd040e6b084@iodoru.org>
2024-02-13 20:01     ` Daniel Simionato
2024-02-11 13:37 ` Arsen Arsenović

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='CAGJwT=_5dAboO3X-2P1XUhdgYOt+FTfO-cxj+o1pR0Lo1bqTGg@mail.gmail.com' \
    --to=daniel.simionato@gmail.com \
    --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