From: "'Antoine Poinsot' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Antoine Riard <antoine.riard@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Public disclosure of 10 vulnerabilities affecting Bitcoin Core < 0.21.0
Date: Wed, 10 Jul 2024 07:40:46 +0000 [thread overview]
Message-ID: <kIhV8zCjV9UxkbWZQRWCiQPj9viUYzO4xAeWBiRCio4w0BeIqAi1weUgs7E7Ftv7w94igEJZtXEmnKMpfHM4VtmPnLrJa8Im26P0QRsWLjI=@protonmail.com> (raw)
In-Reply-To: <a3a30a30-a28b-4348-a0bd-5a70714997e7n@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]
Hey Antoine,
> I think one thing that could be a benefit could be to assign a unique numeric identifier to each sec advisory.
Those are underway. We retro-actively requested CVE numbers for historical issues from Mitre.
Best,
Antoine (the other other one).
On Tuesday, July 9th, 2024 at 3:16 AM, Antoine Riard <antoine.riard@gmail•com> wrote:
> Hello Antoine,
>
> Nothing really new in those 10 security advisories, I think one thing that could be a benefit could be to assign a unique numeric identifier to each sec advisory.
>
> As openssh showed this week this could be good to minimize risks of regressions by favoring methodic screen of old vulnerabilities at review of new changes.
>
> On the security researcher / handler-side, having unique numeric identifiers make it also easier to coordinate mitigation patches development and deployment.
>
> Best,
> Antoine (the other one).
> Le mercredi 3 juillet 2024 à 17:36:02 UTC+1, Antoine Poinsot a écrit :
>
>> Hi everyone,
>>
>> Today we are releasing 10 security advisories for the Bitcoin Core project. Those bugs affect versions of Bitcoin Core before (and not including) 0.21.0.
>>
>> This is part of the gradual adoption by the project of a new vulnerability disclosure policy.
>>
>> The policy and the 10 security advisories can be found on the project's website at https://bitcoincore.org/en/security-advisories .
>>
>> We will follow up later in july to publicly disclose vulnerabilities fixed in version 22.0. And then in august to disclose those fixed in version 23.0, and so on until we run out of old unmaintained versions to disclose vulnerabilities for. The announced policy will then start to be observed for new versions.
>>
>> Antoine Poinsot
>
> --
> 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/a3a30a30-a28b-4348-a0bd-5a70714997e7n%40googlegroups.com.
--
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/kIhV8zCjV9UxkbWZQRWCiQPj9viUYzO4xAeWBiRCio4w0BeIqAi1weUgs7E7Ftv7w94igEJZtXEmnKMpfHM4VtmPnLrJa8Im26P0QRsWLjI%3D%40protonmail.com.
[-- Attachment #2: Type: text/html, Size: 4813 bytes --]
prev parent reply other threads:[~2024-07-10 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 16:34 [bitcoindev] " 'Antoine Poinsot' via Bitcoin Development Mailing List
2024-07-03 17:12 ` [bitcoindev] " Antoine Riard
2024-07-10 7:40 ` 'Antoine Poinsot' via Bitcoin Development Mailing List [this message]
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='kIhV8zCjV9UxkbWZQRWCiQPj9viUYzO4xAeWBiRCio4w0BeIqAi1weUgs7E7Ftv7w94igEJZtXEmnKMpfHM4VtmPnLrJa8Im26P0QRsWLjI=@protonmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=antoine.riard@gmail$(echo .)com \
--cc=darosior@protonmail$(echo .)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