| 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
| ||
|
Message-ID: <0d46ca2b-3cb2-48c0-8e6d-989e1e5f9325@suse.de> Date: Tue, 29 Apr 2025 19:35:41 +0200 From: Hannes Reinecke <hare@...e.de> To: Chaitanya Kulkarni <chaitanyak@...dia.com>, Alistair Francis <alistair23@...il.com>, "hch@....de" <hch@....de>, "sagi@...mberg.me" <sagi@...mberg.me>, "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Alistair Francis <alistair.francis@....com> Subject: Re: [PATCH] nvme-tcp: select tls config when tcp tls is enabled On 4/29/25 18:28, Chaitanya Kulkarni wrote: > On 4/24/25 03:13, Alistair Francis wrote: >> Ensure that TLS support is enabled in the kernel when >> NVME_TARGET_TCP_TLS is enabled. This allows TLS secure channels to be >> used out of the box. >> >> Signed-off-by: Alistair Francis<alistair.francis@....com> > > Looks good. > > Reviewed-by: Chaitanya Kulkarni <kch@...dia.com> > > -ck > Alistair, I think the same fix should be applied to the host side, too; check the last patch of my patch series to convert the authentication code to use the kernel keyring [1]. Should I send out that one as a stand-alone patch to get this issue resolved? [1] https://lore.kernel.org/linux-nvme/20250425094927.102656-13-hare@kernel.org/T/#u Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect hare@...e.de +49 911 74053 688 SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
Powered by blists - more mailing lists