lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVdr0tawKmdMMc0LrjZ7QdTjDw3uk6P+ODgFw3PdE1CkQ@mail.gmail.com>
Date:	Thu, 29 Jan 2015 21:16:36 +0100
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Josh Triplett <josh@...htriplett.org>
Cc:	Iulia Manda <iulia.manda21@...il.com>,
	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Serge Hallyn <serge.hallyn@...onical.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Michal Hocko <mhocko@...e.cz>
Subject: Re: [PATCH v2] kernel: Conditionally support non-root users, groups
 and capabilities

Hi Josh,

On Thu, Jan 29, 2015 at 9:01 PM,  <josh@...htriplett.org> wrote:
>> > +       select NON_ROOT
>>
>> Is there a specific reason why you chose to use "select NON_ROOT"
>> instead of "depends on NON_ROOT" for all these options?
>> As configuring NON_ROOT=n is quite a drastic decision, I don't
>> think you should let that be revertable such easily by all those selects.
>
> In the past, there's been quite a bit of negative feedback about
> "depends on", because that makes various options invisible and
> un-enableable.  (Kconfig can be awkward that way.)  However, I think
> it'd be perfectly reasonable to make all of these "depends on NON_ROOT"
> instead, if there aren't any objections to doing so.

There's been more complaints about select, as it bypasses other
dependencies...

> (As long as we're bikeshedding: CONFIG_MULTIUSER or CONFIG_MULTI_USER?)

(I had checked before)

ARM already has a MULTI_USER define, which does something different.
CIFS has CIFS_MOUNT_MULTIUSER.

So CONFIG_MULTIUSER sounds like the best color ;-)

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ