[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1296042734.10455.45.camel@localhost.localdomain>
Date: Wed, 26 Jan 2011 06:52:14 -0500
From: Mimi Zohar <zohar@...ux.vnet.ibm.com>
To: David Howells <dhowells@...hat.com>
Cc: Roberto Sassu <roberto.sassu@...ito.it>,
linux-security-module@...r.kernel.org, keyrings@...ux-nfs.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
jmorris@...ei.org, safford@...son.ibm.com, ramunno@...ito.it,
tyhicks@...ux.vnet.ibm.com, kirkland@...onical.com
Subject: Re: [RFC][PATCH v3 3/6] encrypted-keys: add key format support
On Wed, 2011-01-26 at 11:03 +0000, David Howells wrote:
> Roberto Sassu <roberto.sassu@...ito.it> wrote:
>
> > This patch introduces a new parameter, called 'format', that defines the
> > format of data stored by encrypted keys. The 'default' format identifies
> > encrypted keys containing only the symmetric key, while other formats can
> > be defined to support additional information. The 'format' parameter is
> > written in the datablob produced by commands 'keyctl print' or
> > 'keyctl pipe' and is integrity protected by the HMAC.
>
> Would it make more sense to take key=val pairs where you have the <format>
> parameter? Then you could have a format=default|foo|whatever argument and
> you'd leave room for future addition of qualifiers.
>
> David
Either way it is extensible. The current format is:
keyctl add encrypted name "new [format] key-type:master-key-name keylen" ring
As none of the other encrypted key parameters are defined as keypairs,
I'd prefer leaving the format option as it is.
thanks,
Mimi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists