grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Escape to CLI (was: Re: [PATCH] broken ESC navigation if authentication is used)
Date: Tue, 10 Nov 2015 21:48:16 +0300	[thread overview]
Message-ID: <56423BF0.1020600@gmail.com> (raw)
In-Reply-To: <201506101829.59882.florian_kaiser@genua.de>

10.06.2015 19:29, Florian Kaiser пишет:
> Hi,
>
> we are using grub2 with authentication enabled and multiple submenus.
> Unfortunately it is not possible to return to a previous menu with ESC without
> triggering a superuser password prompt. This is not the desired behavior in
> my opinion.
> I attached a patch to this email, which removes the password prompt when
> pressing escape.
>

Actually I could not even reproduce it at first. The problem is, new 
submenu opens new context and unless `superusers' is exported as soon as 
we enter submenu no authentication is required at all (including 
entering CLI).

I am not sure whether this is intentional, but this is definitely 
unexpected. And due to complete lack of description of variable scoping 
in GRUB it is also undocumented.

Options are

- simply document variable scoping and mention it in authentication 
description

- propagate superusers to submenus, rely on normal export in nested 
config. Still needs documentation what export actually does.

- export superusers by default and document it in description.


      parent reply	other threads:[~2015-11-10 18:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 16:29 [PATCH] broken ESC navigation if authentication is used Florian Kaiser
2015-06-10 17:02 ` Vladimir 'phcoder' Serbinenko
2015-06-10 19:31 ` Andrei Borzenkov
2015-06-10 19:35   ` Vladimir 'phcoder' Serbinenko
2015-06-11  3:55     ` Andrei Borzenkov
2015-11-08 20:55       ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-10  7:52         ` Andrei Borzenkov
2015-11-12 18:27         ` Andrei Borzenkov
2015-11-10 18:48 ` Andrei Borzenkov [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=56423BF0.1020600@gmail.com \
    --to=arvidjaar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).