From: Jameson Lopp <jameson.lopp@gmail.com>
To: Thomas Pryds <thomas@pryds.eu>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Upcoming DOS vulnerability announcements for Bitcoin Core
Date: Sat, 27 Jun 2015 14:22:01 -0400 [thread overview]
Message-ID: <CADL_X_ejSs6hHahbVyjBjXJxuJjqW9WcNf1HcPGA__hM5w-h7A@mail.gmail.com> (raw)
In-Reply-To: <CAOC2i37rbSbw3ep-JVsGvCuW-KH=knbq6DbCB5z_Z=ZHEtu53g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
According to the release notes, the 0.10.2 release only had notable changes
for Windows. https://bitcoin.org/en/release/v0.10.2
It's not clear that there were any vulnerability patches in 0.10.2 itself
that apply to Ubuntu.
- Jameson
On Sat, Jun 27, 2015 at 1:55 PM, Thomas Pryds <thomas@pryds.eu> wrote:
>
> Den 27/06/2015 08.21 skrev "Gregory Maxwell" <gmaxwell@gmail.com>:
>
> > I strongly recommend anyone running production nodes exposed to inbound
> > connections from the internet upgrade to 0.10.2 as soon as possible.
>
> Does anybody know when/if 0.10.2 will be available on the Ubuntu PPA?
>
> I could of course just install manually, but I like the convenience of a
> PPA.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
[-- Attachment #2: Type: text/html, Size: 1614 bytes --]
next prev parent reply other threads:[~2015-06-27 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-27 6:21 [bitcoin-dev] Upcoming DOS vulnerability announcements for Bitcoin Core Gregory Maxwell
2015-06-27 7:49 ` Wladimir J. van der Laan
[not found] ` <CAOC2i373Bg2v_CHDicn74RFsjZDwwDW5cGQ=01o9YNnU8Tr27w@mail.gmail.com>
2015-06-27 17:55 ` Thomas Pryds
2015-06-27 18:22 ` Jameson Lopp [this message]
2015-06-27 20:53 ` Thomas Pryds
2015-07-07 23:14 ` Gregory Maxwell
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=CADL_X_ejSs6hHahbVyjBjXJxuJjqW9WcNf1HcPGA__hM5w-h7A@mail.gmail.com \
--to=jameson.lopp@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=thomas@pryds.eu \
/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