netdev - Re: Question about nf_conntrack

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: <20190626111322.gks5qptax3iqrjao@breakpoint.cc>
Date:   Wed, 26 Jun 2019 13:13:22 +0200
From:   Florian Westphal <fw@...len.de>
To:     Naruto Nguyen <narutonguyen2018@...il.com>
Cc:     netfilter-devel@...r.kernel.org, netdev@...r.kernel.org,
        netfilter@...r.kernel.org
Subject: Re: Question about nf_conntrack_proto for IPsec

Naruto Nguyen <narutonguyen2018@...il.com> wrote:
> In linux/latest/source/net/netfilter/ folder, I only see we have
> nf_conntrack_proto_tcp.c, nf_conntrack_proto_udp.c and some other
> conntrack implementations for other protocols but I do not see
> nf_conntrack_proto for IPsec, so does it mean connection tracking
> cannot track ESP or AH protocol as a connection. I mean when I use
> "conntrack -L" command, I will not see ESP or AH  connection is saved
> in conntrack list. Could you please help me to understand if conntrack
> supports that and any reasons if it does not support?

ESP/AH etc. use the generic tracker, i.e. only one ESP connection
is tracked between each endpoint.