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]
Message-ID: <496AC2B1.4010603@trash.net>
Date:	Mon, 12 Jan 2009 05:10:25 +0100
From:	Patrick McHardy <kaber@...sh.net>
To:	Andreas Henriksson <andreas@...al.se>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: Problem using iptables MARK from tc.

Andreas Henriksson wrote:
> Hello Patrick and co.
> 
> I was hoping you might have some time to help out with a problem in tc
> related to iptables modules. A bit of historical knowledge about
> libipt_MARK.c is probably useful.
> 
> The full bug-report is available at:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510924
> 
> In iproute2's tc/m_ipt.c there's a function called get_target_name with
> some logic to look up a symbol with the same name as the so-file. (ie.
> "mark" for libipt_MARK.so or libxt_MARK.so).
> There seems to have been a structure with that name in the past, but
> nowadays there are several ones which are jacked in with a registration
> hook.
> 
> Does this sound about right? Do you have any suggestions on how the tc
> modules functionality could be fixed up to find what it needs properly?
> The structures doesn't even seem to be exported in the ABI anymore...

We've added a shared library to iptables so m_ipt doesn't have
to reimplement things, which is pretty much guaranteed to break
occasionally. It doesn't contain all the functionality thats
needed yet, but it should be fairly easy to add. Most likely
you just need to move the code around.

--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ