From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] A policy to support random superuser account names
Date: Fri, 30 Apr 2010 12:36:09 -0700 [thread overview]
Message-ID: <t2lb41005391004301236o493b5966q1d29b28e1ff3919c@mail.gmail.com> (raw)
In-Reply-To: <20100430200726.298ae94c@pomiot.lan>
On Fri, Apr 30, 2010 at 11:07 AM, Michał Górny <gentoo@mgorny.alt.pl> wrote:
> Hello,
>
> I would like to put an emphasis on the fact that many eclasses
> and ebuilds in gx86 are relying on an assumption that the superuser
> account is always supposed to be named 'root'.
>
> In fact, no such constraint exists. Although most users will never even
> think of changing the superuser account name, it is perfectly legit
> to do so, and to use any name for that account. Moreover, it is
> perfectly legit to name an unprivileged user 'root' too.
Whether it is legitimate or not is irrelevant. Users can chose to do
all sorts of legitimate but in the end utterly retarded things to
their systems and developers chose whether or not to support them.
gcc flags are a common case here (I can legitimately set a number of
flags; but most developers ignore reports with odd flags.)
>
> Thus, the above assumption is clearly incorrect and may result in many
> issues with ebuilds using it. These range from builds failing because
> of chown 'invalid user' error to packages being installed with
> incorrect file ownership.
I'd say the assumption is correct in 95% of cases; so it remains a useful one.
>
> From what I've heard already, similar problem has hit Gentoo/*BSD users
> already, with superuser group not being named 'root'. Although some
> files were fixed to properly use numeric GID in the specific case,
> no UID-related changes were done.
>
> Moreover, not all developers agree with the case being an issue,
> and they even refuse patches clearly fixing it [1]. Thus, I guess that
> a clear policy regarding referencing the superuser account should be
> enforced.
Users do a number of utterly ridiculous things to their system and
developers are free to reject bug reports for any number of reasons
(this being one of them.)
>
> In my opinion, that policy should clearly indicate that the numeric
> UID/GID should be always used for referencing the superuser account
> as they are fixed unlike the names.
Except as stated they are not fixed (as Fabian pointed out). I'm
happy to support something like setting ROOT_UID and ROOT_GID in
gentoo-x86 profiles and using those. Then if you want to do something
utterly ridiculous to your system you can just set the appropriate
variables.
This will likely take a GLEP though; plus it is a major change to a
lot of software we have; are you willing to make said changes? Making
a proposal like this is all well and good but you are asking for a lot
of work to be done for what is essentially very little gain for users.
-A
>
> [1] http://bugs.gentoo.org/show_bug.cgi?id=315779
>
> --
> Best regards,
> Michał Górny
>
> <http://mgorny.alt.pl>
> <xmpp:mgorny@jabber.ru>
>
next prev parent reply other threads:[~2010-04-30 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 18:07 [gentoo-dev] A policy to support random superuser account names Michał Górny
2010-04-30 18:29 ` Fabian Groffen
2010-04-30 19:36 ` Alec Warner [this message]
2010-04-30 19:36 ` Alec Warner
2010-05-02 21:57 ` Enrico Weigelt
2010-05-03 7:31 ` Michał Górny
2010-05-04 19:19 ` Mike Frysinger
2010-05-02 15:13 ` Stefan Behte
2010-05-02 15:23 ` Krzysztof Pawlik
2010-05-02 18:52 ` Stefan Behte
2010-05-02 22:06 ` Enrico Weigelt
2010-05-02 22:00 ` Enrico Weigelt
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=t2lb41005391004301236o493b5966q1d29b28e1ff3919c@mail.gmail.com \
--to=antarus@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