netdev - Re: [PATCH] iproute2: Fix building xt module against xtables version 6

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

Date:	Mon, 4 Jul 2011 18:11:35 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Andreas Henriksson <andreas@...al.se>
cc:	shemminger@...tta.com, netdev@...r.kernel.org
Subject: Re: [PATCH] iproute2: Fix building xt module against xtables version
 6

On Monday 2011-07-04 17:17, Andreas Henriksson wrote:

>iptables/xtables apparently changed API again.... Now you need to pass
>and extra parameter (orig_opts) which was not needed before.
>
>Sprinkle some lovely pre-processor magic to be compatible with both older
>and new versions. In the beginning of times XTABLES_VERSION_CODE didn't
>exist. Then it was (0x10000 * major + 0x100 * minor + patch) when it was
>first introduced (according to git), but now it's at 6...
>Don't know what official iptables releases has defined it to over time.

It reflects the soversion, IOW, the ABI (if the developer feels like it, 
also API). This increases only when needed rather than at every release. 
It also won't reach versions >=0x10000 anytime soon because of that. 
More importantly though, the API drafting was just finalized for 1.4.3 
(XTABLES_VERSION_CODE=1), so anything before that is a very blurry 
construct anyway.


>Lets just hope none of the older versions with is has the define
>higher then 6 is still around.... so only the "current" versioning
>scheme is supported.... lets see how long this lasts now.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html