From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1JOIXx-0001JV-5Y
	for mharc-grub-devel@gnu.org; Sun, 10 Feb 2008 15:13:05 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JOIXv-0001JI-UO
	for grub-devel@gnu.org; Sun, 10 Feb 2008 15:13:03 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JOIXv-0001J6-Gq
	for grub-devel@gnu.org; Sun, 10 Feb 2008 15:13:03 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JOIXv-0001J3-Ep
	for grub-devel@gnu.org; Sun, 10 Feb 2008 15:13:03 -0500
Received: from ns39764.ovh.net ([91.121.25.85] helo=nexedi.com)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <okuji@enbug.org>) id 1JOIXv-0005EA-Fr
	for grub-devel@gnu.org; Sun, 10 Feb 2008 15:13:03 -0500
Received: from [10.8.0.46] (unknown [10.8.0.46])
	by nexedi.com (Postfix) with ESMTP id 7E8493EB24
	for <grub-devel@gnu.org>; Sun, 10 Feb 2008 21:20:19 +0100 (CET)
From: "Yoshinori K. Okuji" <okuji@enbug.org>
Organization: enbug.org
To: The development of GRUB 2 <grub-devel@gnu.org>
Date: Sun, 10 Feb 2008 21:13:01 +0100
User-Agent: KMail/1.9.4
References: <20080210130940.GA3879@thorin>
In-Reply-To: <20080210130940.GA3879@thorin>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200802102113.01523.okuji@enbug.org>
X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3)
Subject: Re: [PATCH] implement menu_lock
X-BeenThere: grub-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: The development of GRUB 2 <grub-devel@gnu.org>
List-Id: The development of GRUB 2 <grub-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/grub-devel>
List-Post: <mailto:grub-devel@gnu.org>
List-Help: <mailto:grub-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Feb 2008 20:13:04 -0000

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 interface).

I think this should be named differently. "menu_lock" sounds like freezing a 
menu, but you also disable entering into the command line.

In GRUB Legacy, I used a variable "auth" to define the state of authorization 
(you can have a look at stage2/stage2.c). Was it so bad?

Okuji