From: Ivan Jelincic <parazyd@archlinux.info>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] OpenSSL 1.0.0p / 1.0.1k incompatible, causes blockchain rejection.
Date: Sat, 10 Jan 2015 13:18:31 +0100 [thread overview]
Message-ID: <54B11897.5020100@archlinux.info> (raw)
In-Reply-To: <CA+s+GJCe+6ioiopyfi4eJvFkrPukyW+mMedZ_nKcUEdy-5TEhg@mail.gmail.com>
Is openssl1.0.1j unaffected?
On 01/10/2015 09:35 AM, Wladimir wrote:
> On Sat, Jan 10, 2015 at 4:26 AM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
>> https://github.com/bitcoin/bitcoin/commit/488ed32f2ada1d1dd108fc245d025c4d5f252783
>> (versions of this will be backported to other stable branches soon)
> For those that build from source, patches to cope with the new OpenSSL
> versions are now available on stable branches 0.8, 0.9 and rc branch
> 0.10:
>
> 0.8 branch (on top of 0.8.6)
> ========================
> https://github.com/bitcoin/bitcoin/tree/0.8
> https://github.com/bitcoin/bitcoin/commits/0.8
>
> To fetch, build, and test:
> ```
> git clone -b 0.8 https://github.com/bitcoin/bitcoin.git bitcoin-0.8
> cd bitcoin-0.8/src
> make -f makefile.unix
> make -f makefile.unix check
> ```
>
> 0.9 branch (on top of 0.9.3+)
> ========================
> https://github.com/bitcoin/bitcoin/tree/0.9
> https://github.com/bitcoin/bitcoin/commits/0.9
>
> To fetch, build, and test:
> ```
> git clone -b 0.9 https://github.com/bitcoin/bitcoin.git bitcoin-0.9
> cd bitcoin-0.9/src
> ./autogen.sh
> ./configure
> make
> make check
> ```
>
> 0.10 branch (on top of 0.10.0rc1+)
> ========================
> https://github.com/bitcoin/bitcoin/tree/0.10
> https://github.com/bitcoin/bitcoin/commits/0.10
>
> ```
> git clone -b 0.10 https://github.com/bitcoin/bitcoin.git bitcoin-0.10
> cd bitcoin-0.10/src
> ./autogen.sh
> ./configure
> make
> make check
> ```
>
> Wladimir
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming! The Go Parallel Website,
> sponsored by Intel and developed in partnership with Slashdot Media, is your
> hub for all things parallel software development, from weekly thought
> leadership blogs to news, videos, case studies, tutorials and more. Take a
> look and join the conversation now. http://goparallel.sourceforge.net
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
next prev parent reply other threads:[~2015-01-10 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 4:26 [Bitcoin-development] OpenSSL 1.0.0p / 1.0.1k incompatible, causes blockchain rejection Gregory Maxwell
2015-01-10 5:40 ` Peter Todd
2015-01-10 8:35 ` Wladimir
2015-01-10 12:18 ` Ivan Jelincic [this message]
2015-01-12 9:40 ` Wladimir
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=54B11897.5020100@archlinux.info \
--to=parazyd@archlinux.info \
--cc=bitcoin-development@lists.sourceforge.net \
/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