From: Stephan Mueller <smueller@chronox.de>
To: Kalyani Akula <kalyania@xilinx.com>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 4/5] crypto: Adds user space interface for ALG_SET_KEY_TYPE
Date: Wed, 24 Apr 2019 20:30:35 +0200 [thread overview]
Message-ID: <18759853.IUaQuE38eh@tauon.chronox.de> (raw)
In-Reply-To: <BN7PR02MB5124AC0C75B15E5FB66DF2B6AF220@BN7PR02MB5124.namprd02.prod.outlook.com>
Am Montag, 22. April 2019, 11:17:55 CEST schrieb Kalyani Akula:
Hi Kalyani,
> > Besides, seem to be more a key handling issue. Wouldn't it make sense to
> > rather have such issue solved with key rings than in the kernel crypto
> > API?
>
> [kalyani] Can you please elaborate on this further ?
The kernel has a keyring support in security/keys which has a user space
interface with keyutils. That interface is commonly used for any sort of key
manipulation.
Ciao
Stephan
next prev parent reply other threads:[~2019-04-24 18:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 7:02 [RFC PATCH 0/5] Add Xilinx's ZynqMP AES driver support Kalyani Akula
2019-01-17 7:02 ` [RFC PATCH 1/5] dt-bindings: crypto: Add bindings for ZynqMP AES driver Kalyani Akula
2019-01-17 7:02 ` [RFC PATCH 2/5] ARM64: zynqmp: Add Xilinix AES node Kalyani Akula
2019-01-17 7:02 ` [RFC PATCH 3/5] firmware: xilinx: Add ZynqMP aes API for AES functionality Kalyani Akula
2019-01-17 7:02 ` [RFC PATCH 4/5] crypto: Adds user space interface for ALG_SET_KEY_TYPE Kalyani Akula
2019-01-17 11:34 ` Stephan Mueller
2019-04-22 9:17 ` Kalyani Akula
2019-04-24 18:30 ` Stephan Mueller [this message]
2019-05-08 9:31 ` Kalyani Akula
2019-05-24 6:50 ` Kalyani Akula
2019-05-24 7:19 ` Stephan Mueller
2019-05-24 7:19 ` Stephan Mueller
2019-06-10 5:20 ` Kalyani Akula
2019-06-10 6:35 ` Herbert Xu
2019-06-10 6:35 ` Herbert Xu
2019-07-11 9:25 ` Kalyani Akula
2019-07-11 11:10 ` Herbert Xu
2019-07-11 11:10 ` Herbert Xu
2019-01-17 7:02 ` [RFC PATCH 5/5] crypto: Add Xilinx AES driver Kalyani Akula
2019-01-17 10:33 ` Corentin Labbe
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=18759853.IUaQuE38eh@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kalyania@xilinx.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.