From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH v3] siphash: add cryptographically secure hashtable function Date: Mon, 12 Dec 2016 15:01:00 -0800 Message-ID: <20161212230100.GN8388@tassilo.jf.intel.com> References: <20161212221832.10653-1-Jason@zx2c4.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Linus Torvalds , "kernel-hardening@lists.openwall.com" , LKML , Linux Crypto Mailing List , George Spelvin , Scott Bauer , Andy Lutomirski , Greg KH , Eric Biggers , Jean-Philippe Aumasson , "Daniel J . Bernstein" To: "Jason A. Donenfeld" Return-path: Received: from mga14.intel.com ([192.55.52.115]:1567 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752189AbcLLXBB (ORCPT ); Mon, 12 Dec 2016 18:01:01 -0500 Content-Disposition: inline In-Reply-To: <20161212221832.10653-1-Jason@zx2c4.com> Sender: linux-crypto-owner@vger.kernel.org List-ID: > Dozens of languages are already using this internally for their hash > tables. Some of the BSDs already use this in their kernels. SipHash is > a widely known high-speed solution to a widely known problem, and it's > time we catch-up. It would be nice if the network code could be converted to use siphash for the secure sequence numbers. Right now it pulls in a lot of code for bigger secure hashes just for that, which is a problem for tiny kernels. -Andi