From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Roberto Sassu <roberto.sassu@polito.it>
Cc: linux-security-module@vger.kernel.org, keyrings@linux-nfs.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
David Howells <dhowells@redhat.com>,
James Morris <jmorris@namei.org>,
David Safford <safford@watson.ibm.com>,
Gianluca Ramunno <ramunno@polito.it>,
Tyler Hicks <tyhicks@linux.vnet.ibm.com>,
kirkland@canonical.com
Subject: Re: [RFC][PATCH 1/6] encrypted-keys: fixed valid_master_desc() function description
Date: Fri, 24 Dec 2010 10:45:28 -0500 [thread overview]
Message-ID: <1293205528.3196.22.camel@localhost.localdomain> (raw)
In-Reply-To: <201012231833.59016.roberto.sassu@polito.it>
On Thu, 2010-12-23 at 18:33 +0100, Roberto Sassu wrote:
> Valid key type prefixes for the parameter 'key-type' are: 'trusted' and
> 'user'.
>
> Signed-off-by: Roberto Sassu <roberto.sassu@polito.it>
Thanks Roberto!
Acked-by: Mimi Zohar <zohar@us.ibm.com>
> ---
> security/keys/encrypted_defined.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/security/keys/encrypted_defined.c b/security/keys/encrypted_defined.c
> index 32d27c8..c1c5e27 100644
> --- a/security/keys/encrypted_defined.c
> +++ b/security/keys/encrypted_defined.c
> @@ -84,7 +84,7 @@ static int aes_get_sizes(void)
> /*
> * valid_master_desc - verify the 'key-type:desc' of a new/updated master-key
> *
> - * key-type:= "trusted:" | "encrypted:"
> + * key-type:= "trusted:" | "user:"
> * desc:= master-key description
> *
> * Verify that 'key-type' is valid and that 'desc' exists. On key update,
next prev parent reply other threads:[~2010-12-24 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 17:33 [RFC][PATCH 1/6] encrypted-keys: fixed valid_master_desc() function description Roberto Sassu
2010-12-24 15:45 ` Mimi Zohar [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-23 17:14 Roberto Sassu
2010-12-23 17:28 ` Roberto Sassu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1293205528.3196.22.camel@localhost.localdomain \
--to=zohar@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=kirkland@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=ramunno@polito.it \
--cc=roberto.sassu@polito.it \
--cc=safford@watson.ibm.com \
--cc=tyhicks@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox