Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4203441ybi; Mon, 3 Jun 2019 07:16:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqzPybSFA5um4N4VK1vgds+AyVBHqImatGqairWtgTOgaVivmjrAL7tACDyN0uUKrRS7LFxT X-Received: by 2002:a17:902:4181:: with SMTP id f1mr29067480pld.22.1559571388669; Mon, 03 Jun 2019 07:16:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559571388; cv=none; d=google.com; s=arc-20160816; b=lVNRRqHFK4qU1/fHVCeKrlyC0nJyWDf5OddgNYElJMZHOVebtHrsEQ885JVZcvtRaT w17viaj4QyYwiOqQTxSJtnmp92Mt/ivg7BjWPbcCZJl3ya3INsXTXXJ0MtDn5qAXl5RV 5Tl8zzOHoutexnRrCA/SCHD0k1WJemXt8uHjc02N0CJTsj1sYPyi8ASU33N5+qU77Ry2 PNDRZBwyHGIpBSWT1po5eEWw4r2ct4GhZIDz/shov78FF3KsDelE7vQB03X1/YXy25Hf 3ozsAcCJxRk6AJaTTzY0Anb/ZJvHsvDS9i02D0PokiGsVtsA5UVVu8kNoP8dr5GTAhKU iOxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=oDe9gL9lZNA1VeVKPY+HMRf2GV6VdduVsMVDOR2AvMM=; b=F/Tkvo4V+0IMQGQGBCthnj9bjI7v6jTD+/T49ReqcsS9Jum2maUDVESJpp8SSRWjyD n3LEYDLtL/ZXEEyhOYEixBB8puWKaLvTkX+sKTrnxPgCqzPWRMj0c4gVlE13Bmr9U3/K Cl376nvpfUDqGlkgajykx1BPDYFn0Euv6h8WiVZkDkisnjA03tq79Wgcg8zN/Ff8kKRA WV27GVIiYPmrD0oD0QWOLrZkMGdZ9BpDLET5TmWdwGtESv6ydGACreE82u/62ZwO3KwP YqynPRIXy3JOxvtbsZ3D3hhl0YyHFduBkIg/ra9BSAO9xmQrvdh3eniiUXUDLsmxftdM BNbg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id be3si18153407plb.127.2019.06.03.07.16.07; Mon, 03 Jun 2019 07:16:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727650AbfFCOPs (ORCPT + 99 others); Mon, 3 Jun 2019 10:15:48 -0400 Received: from helcar.hmeau.com ([216.24.177.18]:60672 "EHLO deadmen.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726968AbfFCOPs (ORCPT ); Mon, 3 Jun 2019 10:15:48 -0400 Received: from gondobar.mordor.me.apana.org.au ([192.168.128.4] helo=gondobar) by deadmen.hmeau.com with esmtps (Exim 4.89 #2 (Debian)) id 1hXnkK-0003TA-Vh; Mon, 03 Jun 2019 22:15:33 +0800 Received: from herbert by gondobar with local (Exim 4.89) (envelope-from ) id 1hXnkC-0002q7-KC; Mon, 03 Jun 2019 22:15:24 +0800 Date: Mon, 3 Jun 2019 22:15:24 +0800 From: Herbert Xu To: Harald Freudenberger Cc: Richard Weinberger , Linux Crypto Mailing List , linux-arm-kernel@lists.infradead.org, linux-kernel , linux-imx@nxp.com, festevam@gmail.com, kernel , Sascha Hauer , shawnguo@kernel.org, davem@davemloft.net, david Subject: Re: [RFC PATCH 1/2] crypto: Allow working with key references Message-ID: <20190603141524.wmjmgre4qge7zqjh@gondor.apana.org.au> References: <20190529224844.25203-1-richard@nod.at> <20190530023357.2mrjtslnka4i6dbl@gondor.apana.org.au> <2084969721.73871.1559201016164.JavaMail.zimbra@nod.at> <14ffcdf2-ed9f-be07-fde5-62dfb1fce4f9@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <14ffcdf2-ed9f-be07-fde5-62dfb1fce4f9@linux.ibm.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org 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 Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt