linux-kernel - Re: ipt_MARK/xt

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: <Pine.LNX.4.61.0608221117001.18855@yvahk01.tjqt.qr>
Date:	Tue, 22 Aug 2006 11:17:47 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Patrick McHardy <kaber@...sh.net>
cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	netfilter@...ts.netfilter.org
Subject: Re: ipt_MARK/xt_MARK usage problem

>>>>How do I get MARK back to work in -t filter -- possibly without hacking in 
>>>>xt_MARK.c?
>>>
>>>You won't, its not supposed to work in the filter table.
>> 
>> This worked in 2.6.16, where the ipt_mark_reg_v1 strucutre in xt_MARK.c did 
>> not have a .table limiter. (It also worked in practice, i.e. packets got 
>> marked like they should.) I do not see why this was changed.
>
>That is not true, all versions of the mark target starting in 2.4 had
>the same check in the checkentry function.

Oh sorry I mixed something up. It is CONNMARK which did work (and continues 
to do so) in -t filter... everything fine, sorry for the noise.



Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/