linux-kernel - Re: [PATCH net-next v2 1/3] netlink: specs: fou: change local-v6/peer-v6 check

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m25xe00wd9.fsf@gmail.com>
Date: Wed, 03 Sep 2025 09:32:34 +0100
From: Donald Hunter <donald.hunter@...il.com>
To: Asbjørn Sloth Tønnesen
 <ast@...erby.net>
Cc: "David S. Miller" <davem@...emloft.net>,  Eric Dumazet
 <edumazet@...gle.com>,  Jakub Kicinski <kuba@...nel.org>,  Paolo Abeni
 <pabeni@...hat.com>,  Simon Horman <horms@...nel.org>,  Jacob Keller
 <jacob.e.keller@...el.com>,  "Matthieu Baerts (NGI0)"
 <matttbe@...nel.org>,  David Ahern <dsahern@...nel.org>,  Chuck Lever
 <chuck.lever@...cle.com>,  netdev@...r.kernel.org,
  linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2 1/3] netlink: specs: fou: change
 local-v6/peer-v6 check

Asbjørn Sloth Tønnesen <ast@...erby.net> writes:

> While updating the binary min-len implementation, I noticed that
> the only user, should AFAICT be using exact-len instead.
>
> In net/ipv4/fou_core.c FOU_ATTR_LOCAL_V6 and FOU_ATTR_PEER_V6
> are only used for singular IPv6 addresses, and there are AFAICT
> no known implementations trying to send more, it therefore
> appears safe to change it to an exact-len policy.
>
> This patch therefore changes the local-v6/peer-v6 attributes to
> use an exact-len check, instead of a min-len check.
>
> Signed-off-by: Asbjørn Sloth Tønnesen <ast@...erby.net>

Reviewed-by: Donald Hunter <donald.hunter@...il.com>