From: freeman.zhang1992@gmail.com (Freeman Zhang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to use keyring in the kernel?
Date: Fri, 04 Jul 2014 09:42:49 +0800 [thread overview]
Message-ID: <53B60699.2040700@gmail.com> (raw)
In-Reply-To: <98415.1404398073@turing-police.cc.vt.edu>
Hi,
On Thu, 03 Jul 2014 22:34, Valdis.Kletnieks at vt.edu wrote:
> On Thu, 03 Jul 2014 17:12:15 +0800, Freeman Zhang said:
>
>> And most importantly, what if someone need to manipulate
>> (created, updated and read) keys(not keyring) in kernel
>> services while user key type "aren't intended" for that?
> Why would the kernel be doing that in the first place, when it can
> just use a key that's *not* either a user key or a keyring?
Oh, that's why we should define our own key types.
Thank you Valdis!
Freeman
prev parent reply other threads:[~2014-07-04 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 9:12 How to use keyring in the kernel? Freeman Zhang
2014-07-03 14:34 ` Valdis.Kletnieks at vt.edu
2014-07-04 1:42 ` Freeman Zhang [this message]
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=53B60699.2040700@gmail.com \
--to=freeman.zhang1992@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).