From: Florian Weimer <fw@deneb.enyo.de>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
David MENTRE <dmentre@linux-france.org>,
Gerd Stolpmann <info@gerd-stolpmann.de>,
"Richard W.M. Jones" <rich@annexia.org>,
caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Hardening [Perl's] hash function further
Date: Wed, 20 Nov 2013 19:56:08 +0100 [thread overview]
Message-ID: <878uwinbqv.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <1384859953.62343.YahooMailNeo@web120403.mail.ne1.yahoo.com> (Dario Teixeira's message of "Tue, 19 Nov 2013 03:19:13 -0800 (PST)")
* Dario Teixeira:
> - Any hashtable implementation that uses a non-cryptographic hash function
> and relies on an association list of buckets is vulnerable to attacks
> that force the worst-case O(n) behaviour. Though you can buy some time
> by tweaking the hash function, you are still stuck in an arms race with
> attackers.
You just need a keyed hash with a secret key, not a general-purpose
cryptographic hash function. So far, Jenkins' lookup3 function still
stands.
next prev parent reply other threads:[~2013-11-20 18:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 20:44 Richard W.M. Jones
2013-11-19 0:08 ` Gerd Stolpmann
2013-11-19 7:53 ` David MENTRE
2013-11-19 8:50 ` Richard W.M. Jones
2013-11-19 9:14 ` Gabriel Scherer
2013-11-19 11:19 ` Dario Teixeira
2013-11-19 12:55 ` rixed
2013-11-19 22:18 ` Nicolas Braud-Santoni
2013-11-19 22:39 ` Eric Cooper
2013-11-19 22:55 ` Nicolas Braud-Santoni
2013-11-25 13:46 ` Goswin von Brederlow
2013-11-19 22:31 ` Nicolas Braud-Santoni
2013-11-20 18:56 ` Florian Weimer [this message]
2013-11-20 21:47 ` Gerd Stolpmann
2013-11-25 13:51 ` Goswin von Brederlow
2013-11-25 14:43 ` Yaron Minsky
2013-11-19 22:15 ` Nicolas Braud-Santoni
2013-11-25 13:38 ` Goswin von Brederlow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878uwinbqv.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=caml-list@inria.fr \
--cc=darioteixeira@yahoo.com \
--cc=dmentre@linux-france.org \
--cc=gabriel.scherer@gmail.com \
--cc=info@gerd-stolpmann.de \
--cc=rich@annexia.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).