From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938606AbcLURIo (ORCPT ); Wed, 21 Dec 2016 12:08:44 -0500 Received: from mail-pg0-f65.google.com ([74.125.83.65]:33801 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932859AbcLURIj (ORCPT ); Wed, 21 Dec 2016 12:08:39 -0500 Message-ID: <1482340101.8944.53.camel@edumazet-glaptop3.roam.corp.google.com> Subject: Re: [kernel-hardening] Re: HalfSipHash Acceptable Usage From: Eric Dumazet To: Rik van Riel Cc: kernel-hardening@lists.openwall.com, "Jason A. Donenfeld" , George Spelvin , "Theodore Ts'o" , Andi Kleen , David Miller , David Laight , "Daniel J . Bernstein" , Eric Biggers , Hannes Frederic Sowa , Jean-Philippe Aumasson , Linux Crypto Mailing List , LKML , Andy Lutomirski , Netdev , Tom Herbert , Linus Torvalds , Vegard Nossum Date: Wed, 21 Dec 2016 09:08:21 -0800 In-Reply-To: <1482338385.11006.67.camel@redhat.com> References: <20161221032829.3031.qmail@ns.sciencehorizons.net> <1482298164.8944.8.camel@edumazet-glaptop3.roam.corp.google.com> <1482335804.8944.44.camel@edumazet-glaptop3.roam.corp.google.com> <1482338385.11006.67.camel@redhat.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2016-12-21 at 11:39 -0500, Rik van Riel wrote: > Does anybody still have a P4? > > If they do, they're probably better off replacing > it with an Atom. The reduced power bills will pay > for replacing that P4 within a year or two. Well, maybe they have millions of units to replace. > > In short, I am not sure how important the P4 > performance numbers are, especially if we can > improve security for everybody else... Worth adding that the ISN or syncookie generation are less than 10% of the actual cost of handling a problematic (having to generate ISN or syncookie) TCP packet anyway. So we are talking of minors potential impact for '2000-era' cpus. Definitely I vote for using SipHash in TCP ASAP.