From: patrick <patrick@intersango.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Update alert false positives
Date: Sat, 19 Apr 2014 16:39:51 -0500 [thread overview]
Message-ID: <5352ED27.5080403@intersango.com> (raw)
In-Reply-To: <5352EBDF.2090504@olivere.de>
The alert system filters based on the clients version number.
The ubuntu bitcoin ppa is dynamically linked to openssl unlike the
binaries available from bitcoin.org
There is no way currently to notify users of 0.9.0 w/ static linking
without also notify 0.9.0 w/ dynamic linking.
On 04/19/2014 04:34 PM, Oliver Egginger wrote:
> Hello,
>
> bitcoin-qt produces on many systems an unnecessary alert:
>
> "URGENT: Upgrade required: see https://www.bitcoin.org/heartbleed"
>
> Especially the stable channel is affected:
>
> https://launchpad.net/~bitcoin/+archive/bitcoin
>
> This is a bit frightening for normal users. I think the best would be to
> turn off this message (if possible). It produces too many false
> positives and motivates people to maybe harmful workarounds.
>
> - oliver
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2014-04-19 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 21:34 [Bitcoin-development] Update alert false positives Oliver Egginger
2014-04-19 21:39 ` patrick [this message]
2014-04-19 22:41 ` Jameson Lopp
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=5352ED27.5080403@intersango.com \
--to=patrick@intersango.com \
--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