Topic: Bitcoin Core (Bitcoin-Qt) 0.9.1 released - update required - page 4. (Read 64179 times)
New like these make me wonder if people should avoid new updates if they are not critical. Like an update to 0.9.0 - I did not read changelog and thought, why bother updating...
Does anyone know if this affects Armory wallets? if so, how do we upgrade safely?
Probably, Armory uses the bitcoin daemon.
Just upgrade the bitcoin daemon(packaged with bitcoin-qt/core.)
In reality, I've not seen any evidence to prove this vulnerability could effect a average end bitcoin user behind a router.
EDIT:
Modern routers do more than route network traffic.
They block incoming connections.
My understanding of the heartbleed venerability leads me to believe it would require a open port to request the memory dumps.
I felt I should probably elaborate on my above statement.
Does anyone know if this affects Armory wallets? if so, how do we upgrade safely?
I'm not very happy about the information system. A notification integration that there is a new version available would be the least in the Bitcoin Core.
I wouldn't force the users to upgrade their Bitcoin Core, but at least an Integrated Info-System would be highly apreciated.
That I have to go to the Bitcointalk Forum to read about it, is terrible in my eyes.
It exists. It just wasn't used for 0.9.1. I wouldn't force the users to upgrade their Bitcoin Core, but at least an Integrated Info-System would be highly apreciated.
That I have to go to the Bitcointalk Forum to read about it, is terrible in my eyes.
Thanks for info. Is electrum compromised as well?
I'm not very happy about the information system. A notification integration that there is a new version available would be the least in the Bitcoin Core.
I wouldn't force the users to upgrade their Bitcoin Core, but at least an Integrated Info-System would be highly apreciated.
That I have to go to the Bitcointalk Forum to read about it, is terrible in my eyes.
I wouldn't force the users to upgrade their Bitcoin Core, but at least an Integrated Info-System would be highly apreciated.
That I have to go to the Bitcointalk Forum to read about it, is terrible in my eyes.
Well, one good side effect of this release is that a lot of people will upgrade. Which means more nodes to relay my 0.00001 transaction fee transaction.
Why isn't 0.9.1 on SourceForge, and what is its checksum?
You should be verifying the PGP sigs from https://github.com/bitcoin/gitian.sigs
cd bin - change directory to the bin folder you just unzipped
cd 64 (or 32 depending on your processor) - change directory again to one of two directories inside /bitcoin-blahblahblah/bin/
./bitcoin-qt - execute the binary file
you don't need anything in the src directory, because you want to run a pre-compiled binary (kind of the linux equivalent to a windows .exe file). everything in the src directory is for that.
http://www.devtome.com/doku.php?id=making_a_qt_wallet_work_in_ubuntu_12.04
Thanks, I had resolved the issue by moving bitcoin-qt to the correct directory however this was really helpful in my understanding. cd 64 (or 32 depending on your processor) - change directory again to one of two directories inside /bitcoin-blahblahblah/bin/
./bitcoin-qt - execute the binary file
you don't need anything in the src directory, because you want to run a pre-compiled binary (kind of the linux equivalent to a windows .exe file). everything in the src directory is for that.
http://www.devtome.com/doku.php?id=making_a_qt_wallet_work_in_ubuntu_12.04
Rawted,
Have you tried running bitcoin-qt with -rescan flag?
right click on bitcoin icon. go to properties, and where it says C:\Windows\Program Files(x86)\Bitcoin\bitcoin-blahblahblah.exe (or whatever yours says) add -rescan, run it, and let the blockchain resync.
then go back and remove the flag because you wont want to resync after everytime you run the client.
Have you tried running bitcoin-qt with -rescan flag?
right click on bitcoin icon. go to properties, and where it says C:\Windows\Program Files(x86)\Bitcoin\bitcoin-blahblahblah.exe (or whatever yours says) add -rescan, run it, and let the blockchain resync.
then go back and remove the flag because you wont want to resync after everytime you run the client.
Is there a quick guide to install this ?
I have just switched from windows to Ubuntu, Help!
I got 0.9.0 installed via PPA but the PPA is not updated yet ( + I would like to know how to do it without)
I have :-
Downloaded bitcoin-0.9.1-linux.tar.gz
Then tar xvzf bitcoin-0.9.1-linux.tar.gz
This gives me a folder with bin + src but no ./configure. src has but that fails.
Obviously I just don't get it
I have just switched from windows to Ubuntu, Help!
I got 0.9.0 installed via PPA but the PPA is not updated yet ( + I would like to know how to do it without)
I have :-
Downloaded bitcoin-0.9.1-linux.tar.gz
Then tar xvzf bitcoin-0.9.1-linux.tar.gz
This gives me a folder with bin + src but no ./configure. src has but that fails.
Obviously I just don't get it
cd bin - change directory to the bin folder you just unzipped
cd 64 (or 32 depending on your processor) - change directory again to one of two directories inside /bitcoin-blahblahblah/bin/
./bitcoin-qt - execute the binary file
you don't need anything in the src directory, because you want to run a pre-compiled binary (kind of the linux equivalent to a windows .exe file). everything in the src directory is for that.
http://www.devtome.com/doku.php?id=making_a_qt_wallet_work_in_ubuntu_12.04
Anyone have information on whether this affects multi bit or not?
"@MultiBitOrg Does the OpenSSL bug affect Multibit?"
"-@QuadraQ As MultiBit is installed on your machine you interact with it directly so no."
https://twitter.com/MultiBitOrg
Good to know, thanks for posting! But it's always better to be safe than sorry.
Anyone have information on whether this affects multi bit or not?
"@MultiBitOrg Does the OpenSSL bug affect Multibit?"
"-@QuadraQ As MultiBit is installed on your machine you interact with it directly so no."
https://twitter.com/MultiBitOrg
Anyone have information on whether this affects multi bit or not?
Yes I think separate the core and wallet should be a good thing, but this might require some effort and time, modularization usually take years to achieve
Why isn't 0.9.1 on SourceForge, and what is its checksum?
You should be verifying the PGP sigs from https://github.com/bitcoin/gitian.sigs
Why isn't 0.9.1 on SourceForge, and what is its checksum?
After having read this:
Is there a quick guide to install this ?
I have just switched from windows to Ubuntu, Help!
I got 0.9.0 installed via PPA but the PPA is not updated yet ( + I would like to know how to do it without)
I have :-
Downloaded bitcoin-0.9.1-linux.tar.gz
Then tar xvzf bitcoin-0.9.1-linux.tar.gz
This gives me a folder with bin + src but no ./configure. src has but that fails.
Obviously I just don't get it
I have just switched from windows to Ubuntu, Help!
I got 0.9.0 installed via PPA but the PPA is not updated yet ( + I would like to know how to do it without)
I have :-
Downloaded bitcoin-0.9.1-linux.tar.gz
Then tar xvzf bitcoin-0.9.1-linux.tar.gz
This gives me a folder with bin + src but no ./configure. src has but that fails.
Obviously I just don't get it
The downloaded bin directory contains a few executable files. Find the locations of those files already on your system and replace them with the new versions. Maybe they're in /usr/bin?
...and then this:
If you are using the graphical version of 0.9.0 on any platform, you must update immediately.
If you are using packages from your Linux distro (Ubuntu PPA included), 0.9.1 has no changes for you.Instead, you must upgrade to a fixed OpenSSL version.
...could someone tell me which one is correct please ?
What's the way to follow in order to have it fixed when one has got Bitcoin Core 0.9.0 from Ubuntu PPA ?
Plain English without discrepancies will be much appreciated. Thank you.
I got the message "Corrupted block database detected.
Do you want to rebuild the block database now?" then when it was almost entirely rebuilt I got the message again and it is rebuilding again now-I updated to 0.9.1 between the rebuilt and it didn't change anytging; can someone help me explain?
Do you want to rebuild the block database now?" then when it was almost entirely rebuilt I got the message again and it is rebuilding again now-I updated to 0.9.1 between the rebuilt and it didn't change anytging; can someone help me explain?
Updated to 0.9.1 again, ran it, and now those coins are out of unconfirmed balance and listed as 'conflicted' in transaction log and I don't recognize the address they were sent to.
Jump to: