Return-Path: Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 4494DC000D for ; Wed, 20 Oct 2021 19:38:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 2DCE383B3E for ; Wed, 20 Oct 2021 19:38:07 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.103 X-Spam-Level: X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp1.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=wuille.net Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9STNYLsx5lBs for ; Wed, 20 Oct 2021 19:38:05 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0 Received: from mail-41103.protonmail.ch (mail-41103.protonmail.ch [185.70.41.103]) by smtp1.osuosl.org (Postfix) with ESMTPS id 72EC783B67 for ; Wed, 20 Oct 2021 19:38:05 +0000 (UTC) Received: from mail-0301.mail-europe.com (mail-0301.mail-europe.com [188.165.51.139]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by mail-41103.protonmail.ch (Postfix) with ESMTPS id 4HZLVv2lL4z4wxwK for ; Wed, 20 Oct 2021 19:37:59 +0000 (UTC) Authentication-Results: mail-41103.protonmail.ch; dkim=pass (2048-bit key) header.d=wuille.net header.i=@wuille.net header.b="OuCGzBHj" Date: Wed, 20 Oct 2021 19:37:48 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wuille.net; s=protonmail; t=1634758668; bh=TrSvPT74K7suu3TNpCgjvz9pIJZb89K57oR9u3M1zCY=; h=Date:To:From:Reply-To:Subject:In-Reply-To:References:From; b=OuCGzBHjwlULowdK2dgOlYFegYOouzl7msy65hXkz1FaJShSn5hovCKe/zN6kJ92a OnaYVw9j5VkTHv54hgDEzhvbaFwoQhUnwdmSgOEc7eFDa8x9BLA8RVuSKsEQipUWwZ aTZhknOhxczX7tQ0j/LBj1ooveZYND+9ToELUgah0aCw6ZnV8cdOEswjwXsXlqeO6Y zOxo0IcHsarGJgyrKSmuf1QwP0u6CcL1adpIkagw6eTH/8zcWt67O4SokBrLqEgwXf P4qS/ibI+bsfoBf0r7qlVx5drmGToNcuNSTm143u/MrhsSYKyDPVPOQm9KoAbYGRjQ 5BnE/sqCTGlLQ== To: Owen Gunden , Bitcoin Protocol Discussion From: Pieter Wuille Reply-To: Pieter Wuille Message-ID: In-Reply-To: <20211020192054.GA117785@jauntyelephant.191.37.198.vultr.com> References: <20211020192054.GA117785@jauntyelephant.191.37.198.vultr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 20 Oct 2021 22:14:08 +0000 Subject: Re: [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0 X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2021 19:38:07 -0000 On Wednesday, October 20th, 2021 at 3:20 PM, Owen Gunden via bitcoin-dev wrote: > I also notice that, as of 22.0, Wladimir is no longer signing the > releases, and I have no trust in my gpg network of the people who seem > to have replaced him. This is not correct. Here are Wladimir's attestations on the 22.0 release: = https://github.com/bitcoin-core/guix.sigs/tree/main/22.0/laanwj There is no separate special release key anymore though. Instead, the build= attestations (by anyone) can be used as your trust basis. > Given the level of security at stake here, my eyebrows are raised at > this combination of items changing (new website + new gpg signers at the > same time). There is no new website. The Bitcoin Core project website has been https://= bitcoincore.org for years. I don't know why https://bitcoin.org hasn't upda= ted to list the 22.0 release, though; that's up to them. Cheers, -- Pieter