From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] cli_lock: Added build option to block command line interface
Date: Fri, 26 Jan 2024 23:25:38 +0300 [thread overview]
Message-ID: <CAEaD8JNtNNmoDENPTj=WpTiUxmNVGhvh7BYwxLqNWixc0M6GEw@mail.gmail.com> (raw)
In-Reply-To: <20240126201429.7fw7ju65ebm32kjj@tomti.i.net-space.pl>
[-- Attachment #1.1: Type: text/plain, Size: 1103 bytes --]
Le ven. 26 janv. 2024, 23:15, Daniel Kiper <dkiper@net-space.pl> a écrit :
> On Fri, Jan 26, 2024 at 02:12:31AM +0300, Vladimir 'phcoder' Serbinenko
> wrote:
> > Please detail your use case. GRUB already had user framework in the same
> > problem space.
>
> I am not sure what exactly you mean by "user framework". Could you
> elaborate or point us code examples?
>
https://www.gnu.org/software/grub/manual/grub/grub.html#Authentication-and-authorisation
>
> Anyway, we need a mechanism to disallow access to CLI, arguments editing
> for kernels, etc. I.e. user cannot change widely understood boot config
> even being at the console.
>
Yes and it's exactly what happens as soon as superuser is set. Basically
this patch is equivalent to having a superuser without a valid password.
AFAIR it's achieved by setting superuser's but not issuing password
commands. If not we can have password_deny command.
>
> Daniel
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #1.2: Type: text/html, Size: 2123 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2024-01-26 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 6:26 [PATCH] cli_lock: Added build option to block command line interface Alec Brown
2024-01-24 7:28 ` Olaf Hering
2024-01-26 18:27 ` Daniel Kiper
2024-01-25 23:12 ` Vladimir 'phcoder' Serbinenko
2024-01-26 20:14 ` Daniel Kiper
2024-01-26 20:25 ` Vladimir 'phcoder' Serbinenko [this message]
2024-06-05 13:22 ` Vladimir 'phcoder' Serbinenko
2024-06-05 13:41 ` Daniel Kiper via Grub-devel
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='CAEaD8JNtNNmoDENPTj=WpTiUxmNVGhvh7BYwxLqNWixc0M6GEw@mail.gmail.com' \
--to=phcoder@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 read-only IMAP folder(s) and NNTP newsgroup(s).