Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JOGUB-0004rf-FF for mharc-grub-devel@gnu.org; Sun, 10 Feb 2008 13:01:03 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JOGU9-0004nz-1S for grub-devel@gnu.org; Sun, 10 Feb 2008 13:01:01 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JOGU8-0004mL-23 for grub-devel@gnu.org; Sun, 10 Feb 2008 13:01:00 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JOGU7-0004m2-SR for grub-devel@gnu.org; Sun, 10 Feb 2008 13:00:59 -0500 Received: from mute.marlboro.edu ([206.192.68.75]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JOGU7-0005ct-Pw for grub-devel@gnu.org; Sun, 10 Feb 2008 13:01:00 -0500 Received: from akbar.marlboro.edu (akbar.marlboro.edu [10.1.2.5]) by mute.marlboro.edu (Postfix) with ESMTP id 676AE1F923B for ; Sun, 10 Feb 2008 13:00:36 -0500 (EST) Received: from xyz.marlboro.edu (xyz.marlboro.edu [10.1.2.29]) by akbar.marlboro.edu (Postfix) with ESMTP id 42C1B11E55D for ; Sun, 10 Feb 2008 13:00:36 -0500 (EST) Received: from [10.1.4.164] (mdhcp164.marlboro.edu [10.1.4.164]) by xyz.marlboro.edu (Postfix) with ESMTP id 642593AC3AC for ; Sun, 10 Feb 2008 14:03:30 -0500 (EST) Message-ID: <47AF3BD2.6060305@isaac.cedarswampstudios.org> Date: Sun, 10 Feb 2008 13:00:50 -0500 From: Isaac Dupree User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: The development of GRUB 2 References: <20080210131656.GA4168@thorin> <47AF0282.4000307@isaac.cedarswampstudios.org> <20080210152226.GB7404@thorin> <47AF293F.8070804@isaac.cedarswampstudios.org> <20080210170026.GA12941@thorin> In-Reply-To: <20080210170026.GA12941@thorin> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Marlboro-MailScanner: Found to be clean, clean X-Marlboro-MailScanner-From: id@isaac.cedarswampstudios.org X-Marlboro-MailScanner-Information: Please contact techsupport@marlboro.edu for more information X-Marlboro-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-4.399, required 6, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-MailScanner-From: id@isaac.cedarswampstudios.org X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) Subject: Re: [PATCH] read --echo=[yes|no|wildcard] X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2008 18:01:01 -0000 Robert Millan wrote: > I think that it'd be better to just erase all our environment in > grub_machine_fini() or a similar routine, than to give read specific knowledge > that its data needs this kind of special protection. Besides, it wouldn't be > that simple since the data is controlled by the user via grub.cfg, not directly > by GRUB. I wonder if this erasing would take any significant amount of time (in which case there would be a reason not to implement that to happen all the time) > Anyway, untill we support hashing this doesn't provide any additional security, > since you can get the same from grub.cfg ;-) fairly true, assuming nothing weird happens like grub.cfg being thoroughly deleted in the meantime :-) anyway if a hash is used that takes (by design) around one second on the machine (e.g. sha256 repeated thousands? millions? of times), then I suppose the time taken to erase the memory used by GRUB would be trivial in comparison, assuming(rightly or wrongly) a good implementation... -Isaac