[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161215075746.GA14699@gondor.apana.org.au>
Date: Thu, 15 Dec 2016 15:57:46 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: hannes@...essinduktion.org, netdev@...r.kernel.org,
kernel-hardening@...ts.openwall.com, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, jeanphilippe.aumasson@...il.com,
djb@...yp.to, torvalds@...ux-foundation.org, ebiggers3@...il.com
Subject: Re: [PATCH v2 1/4] siphash: add cryptographically secure hashtable
function
Jason A. Donenfeld <Jason@...c4.com> wrote:
>
> Siphash needs a random secret key, yes. The point is that the hash
> function remains secure so long as the secret key is kept secret.
> Other functions can't make the same guarantee, and so nervous periodic
> key rotation is necessary, but in most cases nothing is done, and so
> things just leak over time.
Actually those users that use rhashtable now have a much more
sophisticated defence against these attacks, dyanmic rehashing
when bucket length exceeds a preset limit.
Cheers,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
