From: Mike Hearn <hearn@vinumeris•com>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Disclosure: consensus bug indirectly solved by BIP66
Date: Wed, 29 Jul 2015 15:41:07 +0200 [thread overview]
Message-ID: <CA+w+GKSNw90FHRKQYvNVNQ=qdCgUL_vAyR8uZ8CJBN3t_A6Zsw@mail.gmail.com> (raw)
In-Reply-To: <55B79146.70309@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
>
> This solved the vulnerability, and opens the door to using non-OpenSSL
> signature verification in the near future.
Great work!
It also means the remaining usages of OpenSSL can be safely replaced with
something like LibreSSL or (perhaps better) BoringSSL.
[-- Attachment #2: Type: text/html, Size: 508 bytes --]
next prev parent reply other threads:[~2015-07-29 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55B78F56.3080802@gmail.com>
2015-07-28 14:27 ` Pieter Wuille
2015-07-29 13:41 ` Mike Hearn [this message]
2015-07-29 13:46 ` Adam Back
2015-07-29 13:48 ` Mike Hearn
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='CA+w+GKSNw90FHRKQYvNVNQ=qdCgUL_vAyR8uZ8CJBN3t_A6Zsw@mail.gmail.com' \
--to=hearn@vinumeris$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pieter.wuille@gmail$(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