Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp482777img; Thu, 28 Feb 2019 02:59:39 -0800 (PST) X-Google-Smtp-Source: AHgI3IYYNVuzruc00EUlFOyd5U3BiL/FNlv0+WRyx2bjGlATqRqv/8qfrBwEfsNmbU79gqRQCmbt X-Received: by 2002:a65:6642:: with SMTP id z2mr7901393pgv.196.1551351579552; Thu, 28 Feb 2019 02:59:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551351579; cv=none; d=google.com; s=arc-20160816; b=mkwdsbVlQ/8KkceVb+UOgUAcQz2JEbAPWEza0P9HadnfnYf0169Uqiq8hLzujxrU73 UmNGafjQkNDiQPj4WKCc2hRn1TllwwV1wXu5KOCLZ6/ptoq5D7whdXnltrCwNrD0Rkwq jtjp1uBqTgiRuygfWL5hQNctPMKNA6bW5ATVmqjrWzhcHs4JUBw0U2Rz1qEmK17zyEKF Pj2pJykvolK+AV+Emuv8zyULDD7QzmdzJPIr6hPbxj2iZS7Bn8VzGw9jB1RW/ql7xigZ amqP7z+Jpf0ReQsPBjxtALDcr5avk6rb/oD3K0tUgFHpoyhhoUnf37iwtiAtbJBJU/qH Ju9Q== 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:to :from:date; bh=y4I2g62aMkL2MT4sJOqlZNtqOamZZ8N8INysu0JHrzI=; b=bwc4jMKzJ9HtuV5OY6LvenJrWcExCpyz1XzF3yja8+KrIS+8doGrdPBv+5/VuSwz7v oXrOvE3jyjbk9k7Vh8gZcHmyReT2liq/6bESAWKPiL/hT6eKosfLZrniIkJ8YF69niIV lEc1GsTAov5cgq7RKTSgQvrGjstvxJ5Qx1Vz/0stOg84bh6gPYTypkM264KGWluj+Zob F0xmBzuaf6VlhhVx66eL1EG9z7T9Z1/gNx97kQCj7Fn32v0+SeNagp1wiefzcHvPIV8G ln2eVMkHHI9tp45+eSBAj+FN3RzJUhLBkTql+JyAIZkmr/agz/0HCaUN92zF44MW4DNS 64Kw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 h189si17141077pge.152.2019.02.28.02.59.24; Thu, 28 Feb 2019 02:59:39 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730987AbfB1Hvy (ORCPT + 99 others); Thu, 28 Feb 2019 02:51:54 -0500 Received: from orcrist.hmeau.com ([104.223.48.154]:42980 "EHLO deadmen.hmeau.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730860AbfB1Hvv (ORCPT ); Thu, 28 Feb 2019 02:51:51 -0500 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 1gzGTo-0007Qk-W3; Thu, 28 Feb 2019 15:51:45 +0800 Received: from herbert by gondobar with local (Exim 4.89) (envelope-from ) id 1gzGTm-00022d-00; Thu, 28 Feb 2019 15:51:42 +0800 Date: Thu, 28 Feb 2019 15:51:41 +0800 From: Herbert Xu To: David Howells , Mimi Zohar , Dmitry Kasatkin , linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 1/4] X.509: Parse public key parameters from x509 for akcipher Message-ID: <20190228075141.s6mftb44yuylbzys@gondor.apana.org.au> References: <20190106133608.820-1-vt@altlinux.org> <20190106133608.820-2-vt@altlinux.org> <20190209214240.56gq7ivn3pw3bssf@altlinux.org> <20190210184628.yupsxgjlaicwbxg6@altlinux.org> <20190219043732.x3sbwzqlz4ikntxo@gondor.apana.org.au> <20190224064840.hii4ccjksjdnewae@altlinux.org> <20190228061444.3escryzoit3idtwg@gondor.apana.org.au> <20190228070449.gjwoq4c2b3x5grie@altlinux.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190228070449.gjwoq4c2b3x5grie@altlinux.org> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 28, 2019 at 10:04:49AM +0300, Vitaly Chikunov wrote: > > It seems that you insist on set_params to be removed and both key and > params to be passed into set_{pub,priv}_key. This means reworking all > existing RSA drivers and callers, right? Can you please confirm that > huge rework to avoid misunderstanding? I don't understand why we even need to touch the existing RSA drivers. Nothing needs to change as far as they're concerned. Only the new algorithms would need to decode the extra parameters in the key stream. Cheers, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt