LKML Archive on
help / color / mirror / Atom feed
From: Herbert Xu <>
To: Harald Freudenberger <>
Cc: Richard Weinberger <>,
	Linux Crypto Mailing List <>,,
	linux-kernel <>,,,
	kernel <>,
	Sascha Hauer <>,,,
	david <>
Subject: Re: [RFC PATCH 1/2] crypto: Allow working with key references
Date: Mon, 3 Jun 2019 22:15:24 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Jun 03, 2019 at 09:59:53AM +0200, Harald Freudenberger wrote:
> The "p" in paes is because we call it "protected key aes". I think you are not limited
> to the "p". What Herbert tries to point out is that you may define your own
> cipher with an unique name and there you can handle your secure key references
> as you like. You may use the s390 paes implementation as a starting point.

Well we have one other driver that is also using the paes name
ccree so I think we should all use this name for hardware keys
with AES.  Only the driver name needs to be unique.

Email: Herbert Xu <>
Home Page:
PGP Key:

      reply	other threads:[~2019-06-03 14:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29 22:48 Richard Weinberger
2019-05-29 22:48 ` [RFC PATCH 2/2] crypto: mxs-dcp: Implement reference keys Richard Weinberger
2019-05-30  2:33 ` [RFC PATCH 1/2] crypto: Allow working with key references Herbert Xu
2019-05-30  7:23   ` Richard Weinberger
2019-06-03  7:59     ` Harald Freudenberger
2019-06-03 14:15       ` Herbert Xu [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [RFC PATCH 1/2] crypto: Allow working with key references' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).