From: Peter Todd <pete@petertodd.org>
To: Niklas Goegge <n.goeggi@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Public disclosure of 2 vulnerabilities affecting Bitcoin Core < v22.0
Date: Wed, 31 Jul 2024 19:01:23 +0000 [thread overview]
Message-ID: <ZqqKA+grzscldhiU@petertodd.org> (raw)
In-Reply-To: <bf5287e8-0960-45e8-9c90-64ffc5fdc9aan@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On Wed, Jul 31, 2024 at 10:01:17AM -0700, Niklas Goegge wrote:
> Hi everyone,
>
> Today we are releasing 2 security advisories for the Bitcoin Core project.
> Those bugs affect versions of Bitcoin Core before (and not including)
> v22.0.
>
> This is part of the gradual adoption by the project of a new vulnerability
> disclosure policy.
>
> The policy and the 2 security advisories can be found on the project's
> website at https://bitcoincore.org/en/security-advisories .
You should say which two security vulnerabilities the newly disclosed ones
actually are. The link does not make that clear at all.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/ZqqKA%2BgrzscldhiU%40petertodd.org.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-07-31 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 17:01 [bitcoindev] Public disclosure of 2 vulnerabilities affecting Bitcoin Core < v22.0 Niklas Goegge
2024-07-31 19:01 ` Peter Todd [this message]
2024-08-04 6:41 ` 'hashnoncemessage' via Bitcoin Development Mailing List
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=ZqqKA+grzscldhiU@petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoindev@googlegroups.com \
--cc=n.goeggi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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