I agree that with this design grub2 lock are somewhat cumbersome to
implement some schemes. I would prefer a user+C-list design. In this
case a following file be used by group
:,,...
:,,...
...
E.g.
root:all
wheel:bootnonet
...
This file can also be reversed and list users per capability instead
On Sunday 10 February 2008 21:59, Robert Millan wrote:
> I didn't see this; it was inspired in the "lock" command in GRUB Legacy.
> But since it only applies to menu, and doesn't lock anything else, I
> thought "menu_lock" would be a good choice.
>
> Since our default state is not to lock the men
On Sun, Feb 10, 2008 at 09:59:48PM +0100, Robert Millan wrote:
>
> menuentry "Only users who unlocked the menu can boot this" {
> if ! test $menu_lock=1 ; then
> multiboot /bar
> fi
> }
>
> menuentry "Only a few selected ones can boot this" {
> echo -n "Password: "
> read password
>
On Sun, Feb 10, 2008 at 09:13:01PM +0100, Yoshinori K. Okuji wrote:
> On Sunday 10 February 2008 14:09, Robert Millan wrote:
> > Implement menu_lock. This is a variable that locks the menu when set.
> >
> > It can be used by users to lock the menu, although there's no way to
> > authenticate users
On Sunday 10 February 2008 14:09, Robert Millan wrote:
> Implement menu_lock. This is a variable that locks the menu when set.
>
> It can be used by users to lock the menu, although there's no way to
> authenticate users for unlocking it, yet (but the procedure would be
> independant from this int
On Sun, Feb 10, 2008 at 02:09:40PM +0100, Robert Millan wrote:
> diff -x configure -x config.h.in -x CVS -x '*~' -x '*.mk' -urp
> ../grub2/normal/misc.c ./normal/misc.c
> --- ../grub2/normal/misc.c2007-10-15 12:59:38.0 +0200
> +++ ./normal/misc.c 2008-02-09 21:32:39.0 +0100
Implement menu_lock. This is a variable that locks the menu when set.
It can be used by users to lock the menu, although there's no way to
authenticate users for unlocking it, yet (but the procedure would be
independant from this interface).
--
Robert Millan
I know my rights; I want my phone
