linux-kernel - Re: [RFC PATCH 1/2] crypto: Allow working with key references

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20190603141524.wmjmgre4qge7zqjh@gondor.apana.org.au>
Date:   Mon, 3 Jun 2019 22:15:24 +0800
From:   Herbert Xu <herbert@...dor.apana.org.au>
To:     Harald Freudenberger <freude@...ux.ibm.com>
Cc:     Richard Weinberger <richard@....at>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
        linux-arm-kernel@...ts.infradead.org,
        linux-kernel <linux-kernel@...r.kernel.org>, linux-imx@....com,
        festevam@...il.com, kernel <kernel@...gutronix.de>,
        Sascha Hauer <s.hauer@...gutronix.de>, shawnguo@...nel.org,
        davem@...emloft.net, david <david@...ma-star.at>
Subject: Re: [RFC PATCH 1/2] crypto: Allow working with key references

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.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt