public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Owen Gunden <ogunden@phauna•org>
To: Prayank <prayank@tutanota•de>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0
Date: Wed, 20 Oct 2021 19:20:54 +0000	[thread overview]
Message-ID: <20211020192054.GA117785@jauntyelephant.191.37.198.vultr.com> (raw)
In-Reply-To: <MmT9umZ--3-2@tutanota.de>

On Wed, Oct 20, 2021 at 04:47:17PM +0200, Prayank wrote:
> > It seems confusing to have two sites that seemingly both represent
> > bitcoin core.
>
> There is only one website which represents Bitcoin Core full node
> implementation. You can download Bitcoin Core from
> https://bitcoincore.org

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.

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).



  reply	other threads:[~2021-10-20 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 14:47 Prayank
2021-10-20 19:20 ` Owen Gunden [this message]
2021-10-20 19:37   ` Pieter Wuille
2021-10-20 19:49     ` Owen Gunden
2021-10-20 19:43   ` Charles Hill
2021-10-20 20:18   ` Kate Salazar
2021-11-05  8:17     ` Prayank
2021-11-05 10:52       ` damian
2021-11-05 14:45       ` yanmaani
2021-11-08  3:02         ` ZmnSCPxj
2021-11-09 12:49         ` Prayank
  -- strict thread matches above, loose matches on Subject: below --
2021-10-20 21:50 Andrew Chow
2021-10-20 12:54 Owen Gunden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211020192054.GA117785@jauntyelephant.191.37.198.vultr.com \
    --to=ogunden@phauna$(echo .)org \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=prayank@tutanota$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox