we need the Bitcoin PPA to be updated to 0.9.1.
unless someone could publish a clear, coherent way to compile the Bitcoin tar.gz
Topic: Bitcoin Core (Bitcoin-Qt) 0.9.1 released - update required - page 3. (Read 64179 times)
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.
Yes sir, and thanks for your help. I replied to your PM. It seems to be almost 2.7btc I am missing now, however only 1.3 btc is showing as unconfirmed in 0.8.6-0.8.9, whereas it's showing as conflicted in 0.9.1. Nothing to the address in question, and none of the tx ids pop up on blockchain.info. 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.
1. Use instructions from this link: http://xmodulo.com/2013/11/create-desktop-shortcut-launcher-linux.html (or google linux+desktop+shortcut)
2. In the “command” field put the correct path to your “bitcoin-qt” file, i.e. “/home/user/bitcoin-0.9.1-linux/bin/64/bitcoin-qt” (without quotes) for example.
3. Uncheck “run in terminal” and check “is executable”, if those checkboxes exist.
4. Use new shortcut (or launcher).
2. In the “command” field put the correct path to your “bitcoin-qt” file, i.e. “/home/user/bitcoin-0.9.1-linux/bin/64/bitcoin-qt” (without quotes) for example.
3. Uncheck “run in terminal” and check “is executable”, if those checkboxes exist.
4. Use new shortcut (or launcher).
Thanks a lot. I will try.
Is Ubuntu ppa:bitcoin/bitcoin going to get updated soon?
Are you going to release ~trusty debs anytime soon?
Are you going to release ~trusty debs anytime soon?
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.
I like to get infos about a new client-version before the last "Sorry all your Bitcoins are stolen" message...
If you talk about the "Alert" function, then Gavin is responsable for the lack of not using it.
I understand that you don't wana use it for bullshit rumors, but the Hardbleed bug is a serious one.
I recommend to use it for all new Bitcoin Core releases. If you don't call it URGENT, then it's just a feature upgrade.
But in this case I think URGENT would have been the right naming for it.
IMHO the risk is being overstated and it probably doesn't warrant the use of the alert key.
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.
I like to get infos about a new client-version before the last "Sorry all your Bitcoins are stolen" message...
If you talk about the "Alert" function, then Gavin is responsable for the lack of not using it.
I understand that you don't wana use it for bullshit rumors, but the Hardbleed bug is a serious one.
I recommend to use it for all new Bitcoin Core releases. If you don't call it URGENT, then it's just a feature upgrade.
But in this case I think URGENT would have been the right naming for it.
How do you compile this on openSUSE? There are no instructions inside this build that explain how to compile/make Bitcoin-Qt/Bitcoind on any version of Linux and what dependencies are needed too. There seems to be a lot of assumptions being made...
The instructions are in src/doc/build-unix.md. For bitcoind, you only need OpenSSL (the fixed version), Boost, and Berkeley DB.
What if I have my blockchain on f drive? How do I update?
Maybe that's how all the darkweb marketplaces and forums got shut down? Utopia was butchered at birth, Black Market Reloaded Forum was also shut down by police.
It is only speculation. The exploit cannot deanonymize hidden service. I can be used to steal private key for .onion address and then impersonate the service. I think the black markets got shut down because of different security issues. 
Maybe that's how all the darkweb marketplaces and forums got shut down? Utopia was butchered at birth, Black Market Reloaded Forum was also shut down by police.
How do you compile this on openSUSE? There are no instructions inside this build that explain how to compile/make Bitcoin-Qt/Bitcoind on any version of Linux and what dependencies are needed too. There seems to be a lot of assumptions being made...
Thanks,
Thanks,
If you are using the graphical version of 0.9.0 on any platform, you must update immediately. Download here. If you can't update immediately, shut down Bitcoin until you can. If you ever used the payment protocol (you clicked a bitcoin: link and saw a green box in Bitcoin Core's send dialog), then you should consider your wallet to be compromised. Carefully generate an entirely new wallet (not just a new address) and send all of your bitcoins there. Do not delete your old wallet.
If you are using any other version of Bitcoin-Qt/Bitcoin Core, including bitcoind 0.9.0, you are vulnerable only if the rpcssl command-line option is set. If it is not, then no immediate action is required. If it is, and if an attacker could have possibly communicated with the RPC port, then you should consider your wallet to be compromised.
This vulnerability is caused by a critical bug in the OpenSSL library used by Bitcoin Core. Successfully attacking Bitcoin Core by means of this bug seems to be difficult in most cases, and it seems at this point that even successful attacks may be limited, but I recommend taking the above actions just in case.
If you are using a binary version of Bitcoin Core obtained from bitcoin.org or SourceForge, then updating your system's version of OpenSSL will not help. OpenSSL is packaged with the binary on all platforms.
Download 0.9.1
Announcement
Other software (including other wallet software) may also be affected by this bug. OpenSSL is extremely common.
If you are using any other version of Bitcoin-Qt/Bitcoin Core, including bitcoind 0.9.0, you are vulnerable only if the rpcssl command-line option is set. If it is not, then no immediate action is required. If it is, and if an attacker could have possibly communicated with the RPC port, then you should consider your wallet to be compromised.
This vulnerability is caused by a critical bug in the OpenSSL library used by Bitcoin Core. Successfully attacking Bitcoin Core by means of this bug seems to be difficult in most cases, and it seems at this point that even successful attacks may be limited, but I recommend taking the above actions just in case.
If you are using a binary version of Bitcoin Core obtained from bitcoin.org or SourceForge, then updating your system's version of OpenSSL will not help. OpenSSL is packaged with the binary on all platforms.
Download 0.9.1
Announcement
Other software (including other wallet software) may also be affected by this bug. OpenSSL is extremely common.
Can someone tell me why the bitcoin-qt file isn't executable in linux?
I use a very simple workaround. I created a shortcut on the desktop and pointed it to the bitcoin-qt file. That's it.Sorry it's all Greek to me I only use Linux for Bitcoin-QT. Can you explain me step by step how I can bitcoin-qt get running. At version 0.8.6. the bitcoin-qt file was executable but in the new version it is a shared libary. I opened the context menu and tried to open the file with "run application" but nothing happens.
2. In the “command” field put the correct path to your “bitcoin-qt” file, i.e. “/home/user/bitcoin-0.9.1-linux/bin/64/bitcoin-qt” (without quotes) for example.
3. Uncheck “run in terminal” and check “is executable”, if those checkboxes exist.
4. Use new shortcut (or launcher).
This is extra bad OpenSSL bug. With Certificate Patrol extension installed on Firefox I see almost every site changing SSL keys. Already changed all my important passwords on websites.
But Bitcoin is not that badly affected. Deep web are changing .onion addresses, people changing TorChat identities. It is chaos there right now and recent attack on Hidden Wiki by some Anonymous moron does not help.
Maybe The Hidden Wiki got it's legendary .onion key leaked because of this OpenSSL vulnerability? This key leaking is exactly what the vulnerability will allow to do. Previously I thought that the hidden wiki's VPS host was broken by password reset.
But Bitcoin is not that badly affected. Deep web are changing .onion addresses, people changing TorChat identities. It is chaos there right now and recent attack on Hidden Wiki by some Anonymous moron does not help.
Maybe The Hidden Wiki got it's legendary .onion key leaked because of this OpenSSL vulnerability? This key leaking is exactly what the vulnerability will allow to do. Previously I thought that the hidden wiki's VPS host was broken by password reset.
Can someone tell me why the bitcoin-qt file isn't executable in linux?
I use a very simple workaround. I created a shortcut on the desktop and pointed it to the bitcoin-qt file. That's it.Sorry it's all Greek to me I only use Linux for Bitcoin-QT. Can you explain me step by step how I can bitcoin-qt get running. At version 0.8.6. the bitcoin-qt file was executable but in the new version it is a shared libary. I opened the context menu and tried to open the file with "run application" but nothing happens.
Can someone tell me why the bitcoin-qt file isn't executable in linux?
I use a very simple workaround. I created a shortcut on the desktop and pointed it to the bitcoin-qt file. That's it. Still missing those coins. It really is quite perplexing. The dates of the transactions with those coins are all from the june/july 2013 range and up until 0.9.1 were valid confirmed coins, and are now conflicted transactions and missing coins. Does this mean I was passed bad transactions previously and it's only now showing up? If so, how were those coins spendable prior?
Do one thing, import wallet on blockchain.info then make a new wallet and send coins to your qt wallet. (Make sure to send a test amount first)
Still missing those coins. It really is quite perplexing. The dates of the transactions with those coins are all from the june/july 2013 range and up until 0.9.1 were valid confirmed coins, and are now conflicted transactions and missing coins. Does this mean I was passed bad transactions previously and it's only now showing up? If so, how were those coins spendable prior?
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...
It's perfectly reasonable to wait a while after a release, and not jump on every update. This is the reason that automatic updates aren't implemented.
Can someone tell me why the bitcoin-qt file isn't executable in linux?
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...
It's perfectly reasonable to wait a while after a release, and not jump on every update. This is the reason that automatic updates aren't implemented.Jump to: