From: Mike Hearn <hearn@vinumeris•com>
To: Adam Back <adam@cypherspace•org>
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:48:16 +0200 [thread overview]
Message-ID: <CA+w+GKQ6hXPjSTLqkOUrtwaXNwhwpY_Lr66ijVWDxoSPL-QO1w@mail.gmail.com> (raw)
In-Reply-To: <CALqxMTHG3aN3gxMBVoviktc0NeO3P6aqzO6vjKZ97Yp+7dQDOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 157 bytes --]
>
> I believe the idea is to replace openSSL with
> https://github.com/bitcoin/secp256k1
Yes, I know. I said "other uses". For example RPC SSL and BIP 70.
[-- Attachment #2: Type: text/html, Size: 470 bytes --]
prev parent reply other threads:[~2015-07-29 13:48 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
2015-07-29 13:46 ` Adam Back
2015-07-29 13:48 ` Mike Hearn [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=CA+w+GKQ6hXPjSTLqkOUrtwaXNwhwpY_Lr66ijVWDxoSPL-QO1w@mail.gmail.com \
--to=hearn@vinumeris$(echo .)com \
--cc=adam@cypherspace$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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