Bitcoin Core (Bitcoin-Qt) 0.9.1 released - update required

[bronan]

I did not had this issue with 0.90 i get and error when it checks the blockchain
The antivirus reports the block data check as containing Trojan: Win32/Malagent
And it also reports to have found DOS/Azusa

This is data being checked by bitcoin-qt in the check files

[1714857168]

1714857168

[1714857168]

1714857168

[1714857168]

1714857168

[1714857168]

1714857168

[1714857168]

1714857168

[mufa23]

Which old clients (if any) are affected? I am still running v0.8.5-beta

[awesomeami]

Which old clients (if any) are affected? I am still running v0.8.5-beta

Better shutdown NOW and upg. ASAP.
What I heard (and don't believe) only 0.9.0.

But I think 0.8.x (and all older) are affected - because OpenSSL contains this bug for 2 years.

Just upg. to 0.9.1

[theymos]

Which old clients (if any) are affected? I am still running v0.8.5-beta

All versions of Bitcoin-Qt are affected by the rpcssl part of the vulnerability if they are linked with an affected OpenSSL version.

[awesomeami]

I did not had this issue with 0.90 i get and error when it checks the blockchain
The antivirus reports the block data check as containing Trojan: Win32/Malagent
And it also reports to have found DOS/Azusa

This is data being checked by bitcoin-qt in the check files

Where did u download this?

[bronan]

From given links in this topic i use the win x64 version on windows 8.1
I am pretty sure its false positive of the av programs

[vapourminer]

just to get this straight..

ALL bitcoint-qt versions have this bug, correct?

how does this bug get triggered? just by having the client running?

or do you need to click a payment link (or something external to the client).. in other words just initiating a transfer via copy/pasteing an address was safe?

[vayvanne]

Did you check control sums? Just offload bitcoin.org a little bit
By the way may this bug be used to empty gox and bitfunder?

[awesomeami]

just to get this straight..

ALL bitcoint-qt versions have this bug, correct?

how does this bug get triggered? just by having the client running?

or do you need to click a payment link (or something external to the client).. in other words just initiating a transfer via copy/pasteing an address was safe?

Here
https://bitcointalk.org/index.php?topic=561923.msg6133060#msg6133060
I suggest every1 to change wallet.
And have more of them and have them OFFLINE!
Online wallets are just for daily spendings.
If u have 5K or 100mil - u still have only few in your wallet and some VISA maybe.
Same for BTC

[bronan]

Well to be sure i rescan now with eset/kapersky and a few others to see if any trojan/virus is found
My weekly scan with my 12 av products was overdue a few days so doing it now
The installer i downloaded from bitcoin.org does seem clean as wel
 

[awesomeami]

Did you check control sums? Just offload bitcoin.org a little bit
By the way may this bug be used to empty gox and bitfunder?

There is no reason to do this.
So grandmas dont get bad habits

[edonkey]

I was using Mac OS X Bitcoin-Qt 0.8.6. As far as I know, I've never used the rpcssl command line option.

So if this rpcssl option is not on by default, then this vulnerability could not have affected me, right?

I've already updated to 0.9.1. I just want to know if I have to go through the emergency measures of creating a new wallet and transferring everything to it.

That's kind of disruptive because it means updating all my miner configs as well. Unless I can preserve my old addresses in the new wallet. Never had to do that so I don't know if it works or not.

[awesomeami]

I was using Mac OS X Bitcoin-Qt 0.8.6. As far as I know, I've never used the rpcssl command line option.

So if this rpcssl option is not on by default, then this vulnerability could not have affected me, right?

I've already updated to 0.9.1. I just want to know if I have to go through the emergency measures of creating a new wallet and transferring everything to it.

That's kind of disruptive because it means updating all my miner configs as well. Unless I can preserve my old addresses in the new wallet. Never had to do that so I don't know if it works or not.

If i would be miner - I would create 3-10 OFFLINE wallets with 10+ adreses each. And then re-conf miners every few weeks with new addr.

New wallet form time to time is a good idea.

And they can still mine (for a time) to old wallet - u just can transfer every X days mined BTC to new wallet...
And slowly change your configs...

Just my 2 satoshis

[Winterfrost]

Did you check control sums? Just offload bitcoin.org a little bit
By the way may this bug be used to empty gox and bitfunder?

SHA-256 checksum of the magnet link matches what I have from the bitcoin.org download.

On the other hand, it's a critical piece of software and only ~60MB; I would still only download from the official source.

[BlockchainHelp?]

I created 4 private keys offline in Bitcoin-QT 9.0 via TailsOS. My client never touched the internet, do I need to bring my cold storage online to create 4 new wallets in 9.1?

[awesomeami]

I created 4 private keys offline in Bitcoin-QT 9.0 via TailsOS. My client never touched the internet, do I need to bring my cold storage online to create 4 new wallets in 9.1?

If wallets were 100% time offline - I think they can't be abused by this bug.

[mufa23]

how does this bug get triggered? just by having the client running?

or do you need to click a payment link (or something external to the client).. in other words just initiating a transfer via copy/pasteing an address was safe?

+1
I want to know as well.

I hate being forced into new updates. Like MoonShadow once said (and I am paraphrasing): "I like to wait until they have ironed out the bugs with new releases before I update". I've been following that same rule, and only update if it's absolutely necessary. Which is why I never even upgraded to v0.9

EDIT: Also, are the cold addresses generated from bitaddress.org safe? Most of my cold Bitcoins are stored on addresses (with their keys) generated from bitaddress.org (i.e. the "Bulk Wallet" option)

[Bitcopia]

how does this bug get triggered? just by having the client running?

or do you need to click a payment link (or something external to the client).. in other words just initiating a transfer via copy/pasteing an address was safe?

+1
I want to know as well.

EDIT: Also, are the cold addresses generated from bitaddress.org safe? Most of my cold Bitcoins are stored on addresses (with their keys) generated from bitaddress.org (i.e. the "Bulk Wallet" option)

I'm also curios. I'd rather not update if not necessary.

If necessary, is a standard update ok? Or is an entirely new wallet required?

[human]

How about alt-coin-wallets based on pre-0.9 code?

[gweedo]

How about alt-coin-wallets based on pre-0.9 code?

Yes alt-coin wallets are affected. Unless they switched out openssl.