netdev - Re: [PATCH v1 0/2] Fix implicit sign conversions in handshake upcall

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <b5db3535a15b7e1bf89724d934fb880d292913cd.camel@redhat.com>
Date: Thu, 21 Sep 2023 10:59:33 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Chuck Lever <cel@...nel.org>, netdev@...r.kernel.org, 
	kernel-tls-handshake@...ts.linux.dev
Cc: Chuck Lever <chuck.lever@...cle.com>
Subject: Re: [PATCH v1 0/2] Fix implicit sign conversions in handshake upcall

Hi,

On Tue, 2023-09-19 at 15:49 -0400, Chuck Lever wrote:
> An internal static analysis tool noticed some implicit sign
> conversions for some of the arguments in the handshake upcall
> protocol.

This does not apply cleanly to -net nor to -net-next, and the lack of
the target inside the subj is confusing. I guess this is for your devel
tree???

Cheers,

Paolo