| 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
| ||
|
Message-ID: <54808123.8000704@redhat.com> Date: Thu, 04 Dec 2014 16:43:31 +0100 From: Daniel Borkmann <dborkman@...hat.com> To: Thomas Graf <tgraf@...g.ch> CC: Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>, "Theodore Ts'o" <tytso@....edu>, netdev@...r.kernel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Where exactly will arch_fast_hash be used On 12/04/2014 04:39 PM, Thomas Graf wrote: > On 12/04/14 at 11:29pm, Herbert Xu wrote: >> On Thu, Dec 04, 2014 at 03:26:37PM +0000, Thomas Graf wrote: >>> >>> As Daniel pointed out, this work originated for the OVS edge use >>> case where security is of less concern and the rehashing is >>> sufficient. Identifying collisions is less of interest as the user >>> space fall back provides a greater surface for an attack. >> >> Well in that case the current setup I think is very misleading. >> It's inviting unsuspecting kernel developers to use it as a hash >> function for general hash tables, which AFAICS is something that >> it fails at miserably. > > Well, it's called fast hash and not secure hash ;-) but a clear hint > definitely wouldn't hurt. Hm, I thought the kernel doc on arch_fast_hash() in include/linux/hash.h would give enough of a hint ... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists