Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1471015pxb; Wed, 12 Jan 2022 15:53:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJwAIwFyapqVoWNijOe9bX//DBWchnDW0n0Fu2Nv288hxhx2l12oCHRJ26Q3j5A7theV+qoX X-Received: by 2002:a05:6402:35c2:: with SMTP id z2mr1891353edc.136.1642031605529; Wed, 12 Jan 2022 15:53:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642031605; cv=none; d=google.com; s=arc-20160816; b=LTyO+v9OgROr3ixI0LHd+7V0+qjX5Dj1ksu7EcBPygVVD8niXuuYLIyH5Mc4/gzg47 HORXwDOzHPOu5ZKCKiNRNxjAz2QmxxosG99viaAK7VX1VnSJ9ZH0mzKsF8sH2zPS7A+N iw2n+Jj3tueYVXXP/YW708kE5UVbv9LSbG2q8vyobMMof/FuueLCx0+Rq8g+lbkF5DP3 wYZxhhawL5qQcqRPpjTiXFrOXY71F9ThCxLcDk046vKZSiUY+Aw4etjJNmO/QgUOdnmy p79yNRjJU1t3JJuPgZ3HewssifkerJpFu7ElpGWFhUYZ6zdPR1EPPkcRRaxbCM3cGOed hoqA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:mail-followup-to:reply-to:message-id :subject:cc:to:from:date:dkim-signature:dkim-signature; bh=9t4ykiev75tOG14agjjEElmq+NfQnoyJeSZiMYsCQ74=; b=w+EavY5JaJSspioiLmBwN2w2EggWD0vWN5eSul67r2nA04AD5PD6x6BtJGEUhK+YQG InmndIqs/ivN/55KGoKA3e3MH8mY8hQOiD+ups6EeAbWM8qQV3K/FqDCIgT94Hfa2hA1 X2jtoB1nOH8Eof/41VpWAk2qL4yX6H/i/0hKuQE+iGGgD3LpJ2lrLXDf6AuXSphPx5SR xl4ohbYGRZ0WIuwBEdI1S9X1Z+ZlambBzHemsnIbQjPn/NLy051uh2wYxpg9tRXn4ryu xi8ARhWk7YTUvLPK1eYRrsYAa+7w9BNNIg4ZJKVTqcGJEczSqevbUSSQItABWmLz88cN lPgA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=GA31Y6uj; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z19si728008edd.422.2022.01.12.15.53.02; Wed, 12 Jan 2022 15:53:25 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=GA31Y6uj; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1356551AbiALSvH (ORCPT + 99 others); Wed, 12 Jan 2022 13:51:07 -0500 Received: from smtp-out2.suse.de ([195.135.220.29]:47228 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243240AbiALSum (ORCPT ); Wed, 12 Jan 2022 13:50:42 -0500 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 2DF391F3A5; Wed, 12 Jan 2022 18:50:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1642013440; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=9t4ykiev75tOG14agjjEElmq+NfQnoyJeSZiMYsCQ74=; b=GA31Y6uj4RTWFy7ndujKKLV9PobXnA2n8kWf7kTlcAmzPRUztdbpshlGKpBa+n2cydTkOx 0dAIzM7Tbqs7BME7KNV+Yy0aU7EFerLGZDANOLYuYcWujWuOXxoySYekI8h2CYsB8iYy6m D45fgjmKCNnez8Zk2QshZuffFBRdzxU= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1642013440; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=9t4ykiev75tOG14agjjEElmq+NfQnoyJeSZiMYsCQ74=; b=CGg0jecFB56y0XEaaS0FixyfA/e3oLE8AuXg4Ao+GCZ4SPBjzxM3XX00hwinwA/AAOmJkh kh2nH7cd0jwzF0Cw== Received: from ds.suse.cz (ds.suse.cz [10.100.12.205]) by relay2.suse.de (Postfix) with ESMTP id B9DC1A3B87; Wed, 12 Jan 2022 18:50:38 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 2B768DA799; Wed, 12 Jan 2022 19:50:05 +0100 (CET) Date: Wed, 12 Jan 2022 19:50:05 +0100 From: David Sterba To: "Jason A. Donenfeld" Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven , Herbert Xu , Ard Biesheuvel , Jean-Philippe Aumasson , linux-crypto@vger.kernel.org Subject: Re: [PATCH RFC v1 0/3] remove remaining users of SHA-1 Message-ID: <20220112185004.GZ14046@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, "Jason A. Donenfeld" , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Geert Uytterhoeven , Herbert Xu , Ard Biesheuvel , Jean-Philippe Aumasson , linux-crypto@vger.kernel.org References: <20220112131204.800307-1-Jason@zx2c4.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220112131204.800307-1-Jason@zx2c4.com> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Wed, Jan 12, 2022 at 02:12:01PM +0100, Jason A. Donenfeld wrote: > Hi, > > There are currently two remaining users of SHA-1 left in the kernel: bpf > tag generation, and ipv6 address calculation. In an effort to reduce > code size and rid ourselves of insecure primitives, this RFC patchset > moves to using the more secure BLAKE2s function. What's the rationale to use 2s and not 2b? Everywhere I can find the 2s version is said to be for 8bit up to 32bit machines and it's worse than 2b in benchmarks (reading https://bench.cr.yp.to/results-hash.html). I'd understand you go with 2s because you also chose it for wireguard but I'd like know why 2s again even if it's not made for 64bit architectures that are preferred nowadays.