Topic: Coins with active devs, per Heartbleed bug example - page 2. (Read 8913 times)
Megacoin has been updated in latest sourceforge version 996G
Ultracoin has the heartbleed fix within 2 weeks
Thanks for making this awesome thread!
Just for the record, Goldcoin (GLD) was updated on April 9th (not the 10th).
https://bitcointalksearch.org/topic/m.6149192
Just for the record, Goldcoin (GLD) was updated on April 9th (not the 10th).
https://bitcointalksearch.org/topic/m.6149192
Please add Machinecoin to the list, it was updated within a day - machinecoin.org
Maybe the bug fix is not yet included in the official Peercoin client (for which is no hurry as Peercoin is not affected from the bug) although the code is ready until 9th of April.
But does that not look like very active development?
http://www.peercointalk.org/index.php?topic=2648.msg22599#msg22599
Read it and make up your own mind what Peershares will do to Peercoin
But does that not look like very active development?
http://www.peercointalk.org/index.php?topic=2648.msg22599#msg22599
Read it and make up your own mind what Peershares will do to Peercoin
Add H2O coin as well.
I'm posting wallets right now.
I'm posting wallets right now.
Though I agree the vulnerability is highly unlikely to effect alt coin clients, I have updated the Windows QT versions of the Star Trek coins along with a routine checkpoint update for all versions.
With all the publicly this vulnerability is getting, I felt that giving users peace of mind was worth the small amount of time needed to update my Windows QT compile environment.
I have started a thread on the SciFi Coin Talk forum announcing the updated clients and welcome any other Scifi coin developer to post announcements pertaining to this there.
http://scificointalk.com/index.php/topic,462.0.html
With all the publicly this vulnerability is getting, I felt that giving users peace of mind was worth the small amount of time needed to update my Windows QT compile environment.
I have started a thread on the SciFi Coin Talk forum announcing the updated clients and welcome any other Scifi coin developer to post announcements pertaining to this there.
http://scificointalk.com/index.php/topic,462.0.html
When you got guys (that may or may not be technical) using your wallet seeing only this 'A bug in OpenSSL, used by Bitcoin-Qt/Bitcoin Core, could allow your bitcoins to be stolen' at the top of their forum and getting worried, I felt it necessary either way.
Coins that are based on bitcoin versions older than 0.9.0 should be fine though, right? Since the bug was only introduced recently and is not present in older openssl versions.
More FUD please.
More FUD please.
Dont tell to many people this or they cant be trendy with their patch.
You dipshits need to realize that the older wallets needed openssl to compile them in the first place.
Might it be that *gasp* there are actual features that rely on the library, namely the rpcssl flag? */gasp* No that can't be, that would be absurd, right?
This isn't about stroking your e-dick as a developer but rather about protecting the users that rely on the feature.
Check this:
Quote
What versions of the OpenSSL are affected?
Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
OpenSSL 1.0.1g is NOT vulnerable
OpenSSL 1.0.0 branch is NOT vulnerable
OpenSSL 0.9.8 branch is NOT vulnerable
http://heartbleed.com/ Status of different versions:
OpenSSL 1.0.1 through 1.0.1f (inclusive) are vulnerable
OpenSSL 1.0.1g is NOT vulnerable
OpenSSL 1.0.0 branch is NOT vulnerable
OpenSSL 0.9.8 branch is NOT vulnerable
Even if there are clients that dont need to update, this is a good "fire drill" for blockchains. If shit really does hit the fan I would rather have my investment in a blockchain with devs that are quick to react.
To the ones saying we can just compile our own clients, that is not the right answer. While most of us are ahead of the curve and can do so, in order to have widespread adoption you will have users who are not as techsavvy. These people will need to depend on those who do know to help them.
To the ones saying we can just compile our own clients, that is not the right answer. While most of us are ahead of the curve and can do so, in order to have widespread adoption you will have users who are not as techsavvy. These people will need to depend on those who do know to help them.
Litecoin
I got the SSL heartbleed email this morning also 
what about NXT? They updated every thing pretty fast.
Whats the point? Lots of coins will get updated with time
This thread makes for a good wake-up call for any devs who are slow with the fix. It's also an info clearing house for anyone wondering about his own coin.
Coins that are based on bitcoin versions older than 0.9.0 should be fine though, right? Since the bug was only introduced recently and is not present in older openssl versions.
More FUD please.
More FUD please.
Dont tell to many people this or they cant be trendy with their patch.
you just have to download new openssl version. build it and compile on it. lool
Anyone who can compile can fix this problem their self just by compiling with the new openssl :O
PHS binaries have been updated
https://bitcointalksearch.org/topic/annphs50-pos-philosopherstone-nopremine-10-month-dist-1641-292720
https://bitcointalksearch.org/topic/annphs50-pos-philosopherstone-nopremine-10-month-dist-1641-292720
Jump to: