From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: dhowells@redhat.com
Cc: linux-kernel@vger.kernel.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org, k.marinushkin@gmail.com
Subject: Re: [PATCH] Security: Keys: Added derived keytype
Date: Wed, 30 Mar 2016 09:34:18 +0200 [thread overview]
Message-ID: <20160330073417.GA18597@gmail.com> (raw)
>> For details see
>> Documentation/security/keys-derived.txt
>
> Usage?
>
> David
You maybe didn't receive my answer sent from gmail web-interface, so I repeat it now from mutt.
Usages of derived keys that I can see:
kernel space:
derive keys from "trusted" (with possibility to access from user space if proper permissions are set);
user space:
store passwords within keyrings;
randomly generated keys, keys with payload given as hex string.
What's your opinion on having derived keytype?
--
Best Regards,
Kirill Marinushkin
next reply other threads:[~2016-03-30 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 7:34 Kirill Marinushkin [this message]
2016-04-01 15:17 ` [PATCH] Security: Keys: Added derived keytype David Howells
-- strict thread matches above, loose matches on Subject: below --
2016-03-22 0:46 Kirill Marinushkin
2016-03-22 2:04 ` kbuild test robot
2016-03-22 9:53 ` David Howells
2016-04-01 15:56 ` David Howells
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=20160330073417.GA18597@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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