ok, finally achieved smackdown by resorting to the SW math. the time i've spent studying & understanding SW has paid huge dividends:
Well both the SW and 2MB options are out in the market now and they can compete for adoption based on user preferences.I had a recent reddit conversation with Adam about that tweet where he said that he has not changed his mind on the 2MB HF, but claimed SF segwit is "safer" & "quicker"
Debian and ubuntu have already released an updated version of the libc6 package to fix the problem:No easy fixes.
- Patch the source code to glibc and recompile is the most straightforward (easiest if your Linux distribution is source-based)
- Disable DNS resolution entirely.
- Wait for your Linux distribution to provide an update
so just apt-get update && apt-get upgrade and you will be safe from this particular security problem./usr/share/doc/libc6/changelog.Debian.gz (Ubuntu 14.04 64bit) said:eglibc (2.19-0ubuntu6.7) trusty-security; urgency=medium
* SECURITY UPDATE: glibc getaddrinfo stack-based buffer overflow
- debian/patches/any/CVE-2015-7547-pre1.diff: fix memory leak in
resolv/nss_dns/dns-host.c.
- debian/patches/any/CVE-2015-7547-pre2.diff: fix memory leak in
include/resolv.h, resolv/gethnamaddr.c, resolv/nss_dns/dns-canon.c,
resolv/nss_dns/dns-host.c, resolv/nss_dns/dns-network.c,
resolv/res_query.c, resolv/res_send.c.
- debian/patches/any/CVE-2015-7547.diff: fix buffer handling in
resolv/nss_dns/dns-host.c, resolv/res_query.c, resolv/res_send.c.
- CVE-2015-7547
Back to normalClassic friendly Antpool is taking a dive in hashrate. I don't like this development.
https://blockchain.info/pools?timespan=24hrs
Do we need a sudo reboot?Debian and ubuntu have already released an updated version of the libc6 package to fix the problem:
so just apt-get update && apt-get upgrade and you will be safe from this particular security problem.
I run my nodes in an opsworks stack. Only the blockchain is on persistent storage. I restart them and they automatically rebuild the entire OS with latest updates and download and compile bitcoin.Do we need a sudo reboot?
Technically true, but a machine reboot after as glibc update is the safest way to make sure you didn't miss something.
Displayed Hashrate is calculated based on blocks found, not measured directly. Blocks found is random with statistical variance.@Norway: I've noticed the hashrate shares vary a lot over fairly short time periods. Last Thursday F2Pool had a 38% share over 24 hours: https://bitco.in/forum/threads/gold-collapsing-bitcoin-up.16/page-327#post-11804
Why this happens I don't know, but I guess short term variation is nothing to worry about.
there's been 3 pops since the bottom. yours, @Peter R's, and now Classic's.You might remember that we had a bit of a pop in the BTC price when BU became a thing. We were joking about it; I didn't take the possible causality seriously. But now we have another pop for classic... this market wants to rise but is being restrained by worries that Bitcoin will be hamstrung by the Core client.