All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: meaning of absent --users prameters.
Date: Sun, 06 Dec 2009 12:50:57 -0600	[thread overview]
Message-ID: <4B1BFD11.70905@gmail.com> (raw)
In-Reply-To: <4B1BF9DE.3070003@gmail.com>

Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Bruce Dubbs wrote:
>> Vladimir 'φ-coder/phcoder' Serbinenko wrote:
>>> Hello. Currently authentication system works as following:
>>>
>>> menuentry "name" --users "a,b,c" {
>>> }
>>> Means that only superusers and users "a", "b" and "c" are permitted to
>>> boot this menuentry. To allow only superusers to boot an entry one would
>>> need:
>>> menuentry "name" --users "" {
>>> }
>>> And absence of --users means "anyone can choose this entry".
>>> Unfortunately this is error-prone. Does anyone oppose to change it to:
>>> No --users: only superusers
>>> To have an unlocked entry you have to add --unlocked
>> First, what is the definition of a 'superuser'?  Where does GRUB get
>> the information to make a decision.
>>
> Superusers are set on per-configuration basis with
> set superusers=<list>
> these users are allowed to invoke shell and edit menu entries so there
> is no reason to restrict which entries they are allowed to boot.
>> In any case, I'd recommend
>>
>>   --users: superusers only
>>
>> or even
>>
>>   --users: superusers
> I don't get what you mean

I thought you were asking about a parameter to the menuentry command

   menuentry "name" --users "a,b,c" {

I was recommending

   menuentry "name" --users superusers {

Where superusers is a keyword implying all superusers.

   -- Bruce



  reply	other threads:[~2009-12-06 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06 18:11 meaning of absent --users prameters Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-06 18:30 ` Bruce Dubbs
2009-12-06 18:37   ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-06 18:50     ` Bruce Dubbs [this message]
2009-12-06 19:08       ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-06 19:13         ` Bruce Dubbs
2010-01-07 19:06 ` Robert Millan

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=4B1BFD11.70905@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=grub-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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.