netdev - Re: [PATCH 4/6] netlink: add strict parsing for future attributes

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: <c85732ca-892e-a1f2-0a52-cbf383a47ab5@6wind.com>
Date:   Fri, 5 Apr 2019 17:22:48 +0200
From:   Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:     Johannes Berg <johannes@...solutions.net>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Cc:     Pablo Neira Ayuso <pablo@...filter.org>,
        David Ahern <dsa@...ulusnetworks.com>,
        Johannes Berg <johannes.berg@...el.com>
Subject: Re: [PATCH 4/6] netlink: add strict parsing for future attributes

Le 04/04/2019 à 08:54, Johannes Berg a écrit :
[snip]
> As we didn't want to add another argument to all functions that get a
> netlink policy, the workaround is to encode that boundary in the first
> entry of the policy array (which is for type 0 and thus probably not
> really valid anyway). I put it into the validation union for the rare
> possibility that somebody is actually using attribute 0, which would
> continue to work fine unless they tried to use the extended validation,
> which isn't likely. We also didn't find any in-tree users with type 0.
OVS_TUNNEL_KEY_ATTR_ID seems to be one if I'm not wrong.


Regards,
Nicolas