netdev - Re: [PATCH 20/38] netns ct: NOTRACK in netns

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: <alpine.LNX.1.10.0809050012400.17569@fbirervta.pbzchgretzou.qr>
Date:	Fri, 5 Sep 2008 00:18:06 -0400 (EDT)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Alexey Dobriyan <adobriyan@...il.com>
cc:	Patrick McHardy <kaber@...sh.net>, netfilter-devel@...r.kernel.org,
	netdev@...r.kernel.org, containers@...ts.linux-foundation.org
Subject: Re: [PATCH 20/38] netns ct: NOTRACK in netns


On Thursday 2008-09-04 22:58, Alexey Dobriyan wrote:

>In conntrack_mt_v0() "ct->status" can be used even for untracked connection,
>is this right?

Yes.

>For example, does setting IPS_NAT_DONE_MASK and IPS_CONFIRMED_BIT on
>untracked conntracked really necessary?

Does it even happen? Something smells afoul if ct->status is anything
but zero/unset for the untracked entry.

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