Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3591109pxv; Mon, 19 Jul 2021 04:12:15 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxQ1SbAfr+QFKuYnoDSrxOjqftRfE26USq1KfP/Rns0QnOGcVO7YHG7+rtXc7uShvAiOk3E X-Received: by 2002:aa7:d990:: with SMTP id u16mr33489111eds.263.1626693134922; Mon, 19 Jul 2021 04:12:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626693134; cv=none; d=google.com; s=arc-20160816; b=RElTr4g16rWS8LdJKHh6gN8GGRvzGsTnh4xcZO1r6wfYME/8ZaHPH/CoJKnR/vwCZn 8GsPoVSzJYGu+PKKlagbvMB9wqiEBhRqWgaxBVIeWyHNUBHPJrKFm8rx9ES3mwPLOur9 cRXvf1qQVpR+eY2T2wlQHO2CblAJyVxHEBJXwoVxZnUF2OhHRConJwSzrPWoc57TzmPJ /QUwdJz9C5Fbk1+YepRhtvYJh9QNBUiEFIc3ZO3Owq2yD+HUbJqNgKX/80y3KeVnyH/M TSinqOrpNQ2vX1+20csVzFw3ub5WpdnkT6QX9IuNV/Jte5z2Af4f6YvWllqi5n8YlY88 sSow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature:dkim-signature; bh=ifLJS6gG3h3JfPSPBAaSbsZ8FktMPmEJAcxEtc8PggA=; b=hFLGgp6EXSGV/Pj4016GblBc63PC7hl5CqFLUHtx0CM6TDeF+T7oqcuW7s/0HGUJPQ 4x6Tdp/NOwwpMevpmPk9MWZSbS5IbCh7HC6OIaNZrgJ2u9fkZ0qSxwABdL9pnaRMp03C D7wg4cl39aXC9G4gF3zFQLcSiYhNKO7WkesaBawWuI96YrKSOS/5s4u1AtBxtHBmGjSm OCsDBMXugdHOX/QJPg5iPFeW/OeZSgRWL0kFTrckZwn+SE8asGMgVj/9nP+lHjBxH0XE FcqXQ22nRl0MVnIwzAOyzStVhrFW/LXL/he//vwC20q4ZQyN8UW7guBsAOUZiu8IBxEL esjA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=Fxodbbgt; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b=Ry4KuHfj; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j5si20459535ejs.749.2021.07.19.04.11.44; Mon, 19 Jul 2021 04:12:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=Fxodbbgt; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b=Ry4KuHfj; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236234AbhGSKap (ORCPT + 99 others); Mon, 19 Jul 2021 06:30:45 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:41708 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236517AbhGSKap (ORCPT ); Mon, 19 Jul 2021 06:30:45 -0400 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 42D0620211; Mon, 19 Jul 2021 11:11:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1626693084; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ifLJS6gG3h3JfPSPBAaSbsZ8FktMPmEJAcxEtc8PggA=; b=FxodbbgtmOviT0rbr5nThGXSmfpNsFhhzGnh+34rmwUWvRWYZIwhC7Tf1cLeZAhcWITV/R S7rWEOU6YYWiFd8rdqhVcI/2jdVBcuRfWtFQvkwCg1Z14B+BEcMBP/rOZJ5hlV5wSB8NmC TbG/h7jaWHG7e6xUNIGznOwncgNkfDI= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1626693084; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ifLJS6gG3h3JfPSPBAaSbsZ8FktMPmEJAcxEtc8PggA=; b=Ry4KuHfjsKJoas5R0+5IIHHudRg08K4HqARIG23oWozAgirg+qjJNbMANujAW4CK1EXbBW y0Z6jGGQdiKahrDw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 3338013CDE; Mon, 19 Jul 2021 11:11:24 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Af0tDNxd9WATSgAAMHmgww (envelope-from ); Mon, 19 Jul 2021 11:11:24 +0000 Subject: Re: [RFC PATCH 00/11] nvme: In-band authentication support To: Simo Sorce , Christoph Hellwig Cc: Sagi Grimberg , Keith Busch , linux-nvme@lists.infradead.org, Herbert Xu , "David S . Miller" , linux-crypto@vger.kernel.org References: <20210716110428.9727-1-hare@suse.de> From: Hannes Reinecke Message-ID: <310097fc-03a9-dc13-6615-2715d59260a2@suse.de> Date: Mon, 19 Jul 2021 13:11:23 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On 7/19/21 12:02 PM, Simo Sorce wrote: > On Fri, 2021-07-16 at 13:04 +0200, Hannes Reinecke wrote: >> Hi all, >> >> recent updates to the NVMe spec have added definitions for in-band >> authentication, and seeing that it provides some real benefit especially >> for NVMe-TCP here's an attempt to implement it. >> >> Tricky bit here is that the specification orients itself on TLS 1.3, >> but supports only the FFDHE groups. Which of course the kernel doesn't >> support. I've been able to come up with a patch for this, but as this >> is my first attempt to fix anything in the crypto area I would invite >> people more familiar with these matters to have a look. >> >> Also note that this is just for in-band authentication. Secure concatenation >> (ie starting TLS with the negotiated parameters) is not implemented; one would >> need to update the kernel TLS implementation for this, which at this time is >> beyond scope. >> >> As usual, comments and reviews are welcome. > > Hi Hannes, > could you please reference the specific standards that describe the > NVMe authentication protocols? > https://nvmexpress.org/wp-content/uploads/NVM-Express-Base-Specification-2_0-2021.06.02-Ratified-5.pdf Section '8.13 NVMe-over-Fabrics In-band authentication' Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@suse.de +49 911 74053 688 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg HRB 36809 (AG Nürnberg), GF: Felix Imendörffer