From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JB6RW-0002QB-Ct for mharc-grub-devel@gnu.org; Sat, 05 Jan 2008 05:39:54 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JB6RU-0002PB-WD for grub-devel@gnu.org; Sat, 05 Jan 2008 05:39:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JB6RT-0002Nc-Lw for grub-devel@gnu.org; Sat, 05 Jan 2008 05:39:51 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JB6RS-0002NH-TQ for grub-devel@gnu.org; Sat, 05 Jan 2008 05:39:51 -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 ) id 1JB6RS-0004NG-7J for grub-devel@gnu.org; Sat, 05 Jan 2008 05:39:50 -0500 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id B35723EB24 for ; Sat, 5 Jan 2008 11:44:40 +0100 (CET) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sat, 5 Jan 2008 11:39:48 +0100 User-Agent: KMail/1.9.4 References: <200801050229.08699.okuji@enbug.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801051139.48591.okuji@enbug.org> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Subject: Re: Transparent decompression with file system filter 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: Sat, 05 Jan 2008 10:39:53 -0000 On Saturday 05 January 2008 07:30, Bean wrote: > I'm thinking that compressed might not be the right word, as filter > doesn't limit to decompression, it can support decryption or format > conversion as well. I guess the name grub_file_open_ex may be better. > I also add a flag to the function, if flag!=0, filters are used, and > if flag=0, grub_file_open_ex is just like grub_file_open. I feel that this is too theoretical. In reality, if you want to support, say, an encrypted file to be decrypted automatically, you need to supply a private key or a passphrase or something like that. How can this be unified and transparent? Okuji