public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "felix-glibc at fefe dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/55815] switch hash function of libstdc++ hash tables to siphash Date: Wed, 23 Sep 2015 02:08:00 -0000 [thread overview] Message-ID: <bug-55815-4-ai3bSQ45bT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55815-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55815 --- Comment #5 from felix-glibc at fefe dot de --- How about you add SipHash and make it selectable at runtime. Then I can file security bugs against all relevant programs not selecting it for being vulnerable and glibc has their ass covered regarding performance. I mean seriously, you argue performance for a security measure? Does Google turn off stack cookies in production? ACL checks? All this password checking is making our code slow? I sure hope not. Also: Do you have any actual benchmarks proving siphash would make a noticeable impact?
next prev parent reply other threads:[~2015-09-23 2:08 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-26 21:39 [Bug libstdc++/55815] New: " felix-gcc at fefe dot de 2013-01-05 13:29 ` [Bug libstdc++/55815] " redi at gcc dot gnu.org 2013-01-05 14:35 ` redi at gcc dot gnu.org 2013-01-05 14:48 ` paolo.carlini at oracle dot com 2015-09-22 22:11 ` gpike at google dot com 2015-09-23 2:08 ` felix-glibc at fefe dot de [this message] 2015-09-23 3:29 ` miyuki at gcc dot gnu.org 2015-09-23 9:56 ` redi at gcc dot gnu.org
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=bug-55815-4-ai3bSQ45bT@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).