From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 95FC31396D9 for ; Thu, 19 Oct 2017 22:33:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1A15B2BC0A4; Thu, 19 Oct 2017 22:33:29 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id B72042BC04B for ; Thu, 19 Oct 2017 22:33:28 +0000 (UTC) Received: from pc1 (unknown [IPv6:2001:2012:127:3e00:b3bf:56a1:a140:6086]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: hanno) by smtp.gentoo.org (Postfix) with ESMTPSA id 016C333BF0B for ; Thu, 19 Oct 2017 22:33:26 +0000 (UTC) Date: Fri, 20 Oct 2017 00:32:58 +0200 From: Hanno =?UTF-8?B?QsO2Y2s=?= To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Manifest2 hashes, take n+1-th Message-ID: <20171020003258.7ad4695b@pc1> In-Reply-To: <1508440120.19870.14.camel@gentoo.org> References: <1508440120.19870.14.camel@gentoo.org> X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 416da1ee-561f-41c6-ae5a-332532d378ee X-Archives-Hash: 18474c2cbc9cfaf01a04283602c24bf5 On Thu, 19 Oct 2017 21:08:40 +0200 Micha=C5=82 G=C3=B3rny wrote: > manifest-hashes =3D SHA512 SHA3_512 Counterproposal: Just use SHA512. There isn't any evidence that any SHA2-based hash algorithm is going to be broken any time soon. If that changes there will very likely be decades of warning before a break becomes practical. Having just one hash is simpler and using a well supported one like SHA512 may make things easier than using something that's still not very widely supported. --=20 Hanno B=C3=B6ck https://hboeck.de/ mail/jabber: hanno@hboeck.de GPG: FE73757FA60E4E21B937579FA5880072BBB51E42