From: Niklas Goegge <n.goeggi@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Public disclosure of 2 vulnerabilities affecting Bitcoin Core < v22.0
Date: Wed, 31 Jul 2024 10:01:17 -0700 (PDT) [thread overview]
Message-ID: <bf5287e8-0960-45e8-9c90-64ffc5fdc9aan@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]
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 .
We will follow up later in August to publicly disclose vulnerabilities
fixed in version v23.0. And then in September to disclose those fixed in
version v24.0, and so on until we run out of unmaintained versions to
disclose vulnerabilities for. The announced policy will then start to be
observed for new versions.
Niklas Gögge
--
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/bf5287e8-0960-45e8-9c90-64ffc5fdc9aan%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1553 bytes --]
next reply other threads:[~2024-07-31 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 17:01 Niklas Goegge [this message]
2024-07-31 19:01 ` Peter Todd
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=bf5287e8-0960-45e8-9c90-64ffc5fdc9aan@googlegroups.com \
--to=n.goeggi@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/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