netdev - Re: [PATCH net] xfrm: Clear sk_dst_cache when applying per-socket policy.

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: <CAKD1Yr3uJCSBPtCds+ckXDusmCC-qMojDjtMFa1UAm_vcR1cUg@mail.gmail.com>
Date:   Wed, 16 Aug 2017 18:03:17 +0900
From:   Lorenzo Colitti <lorenzo@...gle.com>
To:     Jonathan Basseri <misterikkit@...gle.com>
Cc:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>, jkbs@...hat.com,
        David Miller <davem@...emloft.net>,
        Steffen Klassert <steffen.klassert@...unet.com>
Subject: Re: [PATCH net] xfrm: Clear sk_dst_cache when applying per-socket policy.

On Wed, Aug 16, 2017 at 7:25 AM, Jonathan Basseri
<misterikkit@...gle.com> wrote:
> If an IPv6 socket has a valid dst cache

Did you look into why IPv4 does not suffer from this problem?

That said, clearing the dst cache entry does seem prudent in general.