OpenSSL 'heartbleed' bug exposes memory blocks - including passwords. - page 2.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: Bit_Happy on April 08, 2014, 05:06:41 PM

Does anyone know if Cryptsy updated yet?
EDIT:
We have updated all of our OpenSSL servers and our DDOS provider has also updated. More information here: http://blog.cryptsy.com

...or btc-e?
On April 6th
"We updated SSL certificate"
...That may have simply been expiring. Cannot tell what version of OpenSSL they are running.

I don't vouch for the accuracy of this test but it indicates no vulnerability
http://filippo.io/Heartbleed/#cryptsy.com

Bit_Happy

legendary

Activity: 2114

Merit: 1040

A Great Time to Start Something!

Does anyone know if Cryptsy updated yet?
EDIT:
We have updated all of our OpenSSL servers and our DDOS provider has also updated. More information here: http://blog.cryptsy.com

...or btc-e?
On April 6th
"We updated SSL certificate"
...That may have simply been expiring. Cannot tell what version of OpenSSL they are running.

DeathAndTaxes

donator

Activity: 1218

Merit: 1079

Gerald Davis

Quote from: Robert Paulson on April 08, 2014, 04:56:51 PM

SSL can now be considered as dead, this bug leaks the private SSL key of all the websites that use SSL.
even if they patch the server anyone who dumped enough of the server's memory would likely be able to recover the SSL private key of the server.

Generating a new key and cert as well as revoking the old cert takes less than an hour (honestly more like ten minutes but was being conservative). Of course many website were completely unaffected as they didn't use the compromised version of OpenSSL. BitSimple (among many other Bitcoin related sites) for example is unaffected.

bitpop

legendary

Activity: 2912

Merit: 1060

Quote from: Robert Paulson on April 08, 2014, 04:56:51 PM

SSL can now be considered as dead, this bug leaks the private SSL key of all the websites that use SSL.
even if they patch the server anyone who dumped enough of the server's memory would likely be able to recover the SSL private key of the server.

Re keying is easy if the site cares

Robert Paulson

sr. member

Activity: 448

Merit: 250

SSL can now be considered as dead, this bug leaks the private SSL key of all the websites that use SSL.
even if they patch the server anyone who dumped enough of the server's memory would likely be able to recover the SSL private key of the server.

turio

newbie

Activity: 14

Merit: 0

this is a serious concern and everyone should patch up

bitpop

legendary

Activity: 2912

Merit: 1060

It's out https://bitcoin.org/bin/0.9.1/

bitpop

legendary

Activity: 2912

Merit: 1060

This bug must be intentional

Cryddit

legendary

Activity: 924

Merit: 1132

As far as I can see, this bug affects bitcoind in the case that you use RPC over a network to access your wallet.

If you don't, I don't believe there's any vulnerability that this exposes. (This is a quick examination only; there could be something I missed). If you have, and someone who knew about this bug was paying attention at the time, then that person may have your password.

OTOH, I think this explains the widespread SSL break implied by the Snowden papers.

EDIT:

I had not looked at the new payment protocol stuff with the recent client. It is also exposed to this bug. So, if you have used the payment prototocol over the network, you have been exposed.

Bit_Happy

legendary

Activity: 2114

Merit: 1040

A Great Time to Start Something!

Next up is huge concern about the exchanges that have not updated.

Quote from: windpath on April 08, 2014, 03:52:10 PM

Gavin Andresen: Expect Bitcoin Core 0.9.1 Release Soon Because of Heartbleed OpenSSL Bug

http://newsbtc.com/2014/04/08/gavin-andresen-expect-bitcoin-core-0-9-1-release-soon-heartbleed-openssl-bug/

EDIT:
The vulnerability does not affect the bitcoin protocol or wallet. It may affect auxilary usage of TLS in RPC-over-SSL and when fetching payment requests over HTTPS.

Not a big deal, but we are going to release a 0.9.1 that updates OpenSSL (see pull #4023 if you want to test) and fixes some other minor issues from 0.9.0.

windpath

legendary

Activity: 1258

Merit: 1027

Gavin Andresen: Expect Bitcoin Core 0.9.1 Release Soon Because of Heartbleed OpenSSL Bug

http://newsbtc.com/2014/04/08/gavin-andresen-expect-bitcoin-core-0-9-1-release-soon-heartbleed-openssl-bug/

Bit_Happy

legendary

Activity: 2114

Merit: 1040

A Great Time to Start Something!

Thanks for posting a serious story.

What should a website operator do about the Heartbleed OpenSSL exploit?
http://security.stackexchange.com/questions/55076/what-should-a-website-operator-do-about-the-heartbleed-openssl-exploit

bitpop

legendary

Activity: 2912

Merit: 1060

Quote from: ?? on ??

Quote from: bitcoiner49er on April 08, 2014, 01:04:44 PM

When will you know that https://"XYZ" has secured itself against this?

http://filippo.io/Heartbleed/

http://filippo.io/Heartbleed/#apicoin.io << my site is secured, I was one of the first since I saw this on a netsec newsletter last night.

https://apicoin.io/register/error1

bitcoiner49er

sr. member

Activity: 457

Merit: 250

Nevermind

blacksails

sr. member

Activity: 294

Merit: 250

Quote from: Cryddit on April 08, 2014, 12:41:20 PM

OpenSSL has been revealed to have a huge gaping hole.

http://www.bbc.com/news/technology-26935905

Those who have been securing communications using https (which is essentially all of us) should change all passwords they have used with those systems.

Those who have used the same password in https that they have used to encrypt their wallets - yeah, you can figure that out, right? An attacker may have the old password. You should be using a different one.

This is quite bad. That'd mean I'd have to change almost all of my passwords… Geez, that will take some time!
At least my wallet is encrypted with a completely different password.

Cryddit

legendary

Activity: 924

Merit: 1132

OpenSSL has been revealed to have a huge gaping hole.

http://www.bbc.com/news/technology-26935905

Those who have been securing communications using https (which is essentially all of us) should change all passwords they have used with those systems.

Those who have used the same password in https that they have used to encrypt their wallets - yeah, you can figure that out, right? An attacker may have the old password. You should be using a different one.

Topic: OpenSSL 'heartbleed' bug exposes memory blocks - including passwords. - page 2. (Read 5230 times)