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: <CANn89iKUtN3gO1rndW-2yNsOZian4OngnLUxLWqfo4VRb73-kA@mail.gmail.com>
Date:   Fri, 14 Jun 2019 08:51:33 -0700
From:   Eric Dumazet <edumazet@...gle.com>
To:     Jason Baron <jbaron@...mai.com>
Cc:     Ard Biesheuvel <ard.biesheuvel@...aro.org>,
        netdev <netdev@...r.kernel.org>, linux-crypto@...r.kernel.org,
        Herbert Xu <herbert@...dor.apana.org.au>, ebiggers@...nel.org,
        David Miller <davem@...emloft.net>,
        Christoph Paasch <cpaasch@...le.com>,
        David Laight <David.Laight@...lab.com>,
        Yuchung Cheng <ycheng@...gle.com>
Subject: Re: [PATCH v2] net: ipv4: move tcp_fastopen server side code to
 SipHash library

On Fri, Jun 14, 2019 at 8:44 AM Jason Baron <jbaron@...mai.com> wrote:
>
>
>
>
> The inconsistencies coming from kernel version skew with some servers
> being on the old hash and some on the newer one? Or is there another
> source for the inconsistency you are referring to?
>

The servers still using the old crypto hash, and the new servers using
the new siphash,
will generate different fastopen cookies, even if fed with the same
key (shared secret
among all the server farm)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ