Pages:
Author

Topic: Bitcoin-Qt / bitcoind version 0.8.4 released, fixes critical DoS vulnerability - page 2. (Read 40396 times)

full member
Activity: 238
Merit: 100
Love the Bitcoin.
very nice and thank you very much!
donator
Activity: 406
Merit: 252
Study the past, if you would divine the future.
There seems to be a major bug in the Mac version, it keeps showing and error in the database and makes me re-download the blockchain everytime I try to open the client. I had to revert back to the old version to be able to download the blockchain and access my wallet.
full member
Activity: 156
Merit: 102
Bean Cash - More Than a Digital Currency!
Thanks, guys!  Upgraded and running without a hitch... Grin
hero member
Activity: 503
Merit: 501
Crashes on Synchronizing. Using Win7 pro, when i install and run the application kills Security Essentials.
What does "kills Security Essentials" mean? Do you get a error message?


'Security Essentials has stopped working', after fiddling, it appears that SE didn't have the latest virus definitions and would stop working during any scans. This was coincident with installing the latest wallet as linked above. I've already removed anything I could find on this computer relating to bitcoin. I believe when I first DL Bitcoin Wallet and initialized the application it was about 7 weeks behind the network and during the synchronization, when I got the first message (Security Essentials has stopped working). Rebooted, the anti-virus started up normally, ran bitcoin the AV crashed - 'stopped working' again, but this time i was only 4 weeks behind synchronizing with network. Rebooted again, got SE to update virus definitions and I'm back attempting to synchronize with the network again.

Here's where I am with the Synchronizing now... 250723 of 256455 (estimated) 8 active connections to bitcoin network, version located in registry is 0.8.4, (i searched registry for 'bitcoin' and only find references to Bitcoin-qt.exe just to see if there's any remnants of previous installs)

Have to go out for a couple of hours and I'm leaving the wallet up to see if it will sync.

*corrected the estimated blocks. It's been an hour, synchronizing won't go past 250723. Uninstalling the application.
sr. member
Activity: 280
Merit: 250

Nice to see comprehensive upgrades of Bitcoin rolling out like clockwork.
staff
Activity: 4172
Merit: 8419
Crashes on Synchronizing. Using Win7 pro, when i install and run the application kills Security Essentials.
What does "kills Security Essentials" mean? Do you get a error message?
hero member
Activity: 503
Merit: 501
Crashes on Synchronizing. Using Win7 pro, when i install and run the application kills Security Essentials.

I purchased some block erupters and can't install the software for those either. At this point I've got no working wallet software and no working mining software.

Edit: uninstalled anything I could find bitcoin related. Cleaned up registry, rebooted and I'm back to Sync wallet. It crashed Microsoft Security Essentials again so I'm just leaving it off while the Wallet syncs up.
staff
Activity: 4172
Merit: 8419
Thank you for your assistance, I appreciate it immensely!
The transaction looks fine, I don't see any reason it wouldn't have been relayed by all nodes— perhaps you had a network burp at the wrong moment, and it would have handled it fine with a retransmission.

I went ahead and rebroadcasted your transaction... (by running sendrawtransaction ) and see it on a couple nodes.
newbie
Activity: 47
Merit: 0
I upgraded to 0.8.4 on OS X 10.8 without issue, no DB corruption or whatnot, HOWEVER, now I made my first transaction since upgrading and I can't get the transaction to confirm, it has been 1.5 hours since the transaction and NOTHING... ZERO confirmations. It says the following: Status: 0/unconfirmed, broadcast
Your transaction should be fine if you just leave your node running it will rebroadcast it periodically.

To be more sure about it, open up the debug console (help -> debug -> console) and type

getrawtransaction 1

e.g.

getrawtransaction eb61f51fe142ff46958cf1f98d31a1a5cdbcab4a766b711fc9f2fb8e2cb4504f 1

And paste the result and we can look at the transaction and potentially rebroadcast it.


Thank you for your assistance, I appreciate it immensely!

14:54:35

redacted to prevent any issues
staff
Activity: 4172
Merit: 8419
I upgraded to 0.8.4 on OS X 10.8 without issue, no DB corruption or whatnot, HOWEVER, now I made my first transaction since upgrading and I can't get the transaction to confirm, it has been 1.5 hours since the transaction and NOTHING... ZERO confirmations. It says the following: Status: 0/unconfirmed, broadcast
Your transaction should be fine if you just leave your node running it will rebroadcast it periodically.

To be more sure about it, open up the debug console (help -> debug -> console) and type

getrawtransaction 1

e.g.

getrawtransaction eb61f51fe142ff46958cf1f98d31a1a5cdbcab4a766b711fc9f2fb8e2cb4504f 1

And paste the result and we can look at the transaction and potentially rebroadcast it.
newbie
Activity: 47
Merit: 0
I upgraded to 0.8.4 on OS X 10.8 without issue, no DB corruption or whatnot, HOWEVER, now I made my first transaction since upgrading and I can't get the transaction to confirm, it has been 1.5 hours since the transaction and NOTHING... ZERO confirmations. It says the following: Status: 0/unconfirmed, broadcast through 119 nodes
Date: 9/5/13 13:04
Debit: -0.35 BTC
Transaction fee: -0.00004 BTC
Net amount: -0.35004 BTC
Transaction ID: eb61f51fe142ff46958cf1f98d31a1a5cdbcab4a766b711fc9f2fb8e2cb4504f

The transaction was .35 btc and I payed a .00004 fee to the network and it is stuck... I look up the transaction id and it doesn't exist...
I just lost my bitcoin, what can I do?

I don't have anymore coins to try another transaction and I am really bummed out about this
legendary
Activity: 1526
Merit: 1129
I think the Ubuntu PPA is maintained by Matt, whose credibility and honesty is above question.
legendary
Activity: 1220
Merit: 1015
e-ducat.fr
Updated on OSX and Win7 without a glitch. Many thanks to the dev team.
sr. member
Activity: 300
Merit: 250
Thanks for the update! Upgrading now...  Wink
legendary
Activity: 1500
Merit: 1021
I advocate the Zeitgeist Movement & Venus Project.
Win7x64 operating without issue.
member
Activity: 115
Merit: 10
Roger that upgrading now thanks as always to the devs

+ Thanks a million to all the Dev, will go update. Smiley
hero member
Activity: 802
Merit: 1003
GCVMMWH
I am unable to compile 0.8.4 in Debian 7. I checked out 0.8.3 and was able to compile with no issues. When I switch back to 0.8.4 I get the following:

Your paste indicates you are building the development version (master, aka pre-0.9), not 0.8.4 release.

Your 0.9 build fails due to lack of the protobufs compiler, "protoc"

You want to check out the v0.8.4 branch.

Yep - I checked out  v0.8.4r2 and it worked. I'm guessing that a lot of folks are just going to git clone https://github.com/bitcoin/bitcoin.git and get the same issue though.
Anyway, thanks for the update.
staff
Activity: 4172
Merit: 8419
It was not meant as criticism of the dev team. You all do a great job. It can't be as I don't know how to do it better. It is meant to raise awareness of how many people actually blindly install anything that comes as bitcoin.exe. The "criticism" also contains "it's maybe a lack of tools or maybe a lack of understanding on my side". It is a fact that the majority of users install without ever checking a sig.
You have my complete agreement there. In the future we should use an updater program (e.g. "gitian updater") which checks the signature for the users, so at least once users have one good copy they should be okay on future ones.
legendary
Activity: 1862
Merit: 1105
WalletScrutiny.com
could anyone loose coins as a result of the bugs fixed in this release?

No. The whole network could be shut down, but the coins would stay put.
Thanx.

My other question: To have multiple people confirm the quality of a binary, can they compile it separately, getting the same binary? I would love to see as many people that review code to sign the binaries to gain trust. The source being trustful and the binary being signed by just one person is kind of a joke with the money at stake. No offense, Gavin, you are doing a great job and it's maybe a lack of tools or maybe a lack of understanding on my side (which would be a lack of easy and well known tools) but I think this update process needs more trust.
Uhhh.

Our binaries are bit-reproducible, and are always authenticated by multiple parties before being posted: https://github.com/bitcoin/gitian.sigs

We are innovators in this space, your criticism here is really misplaced.

It was not meant as criticism of the dev team. You all do a great job. It can't be as I don't know how to do it better. It is meant to raise awareness of how many people actually blindly install anything that comes as bitcoin.exe. The "criticism" also contains "it's maybe a lack of tools or maybe a lack of understanding on my side". It is a fact that the majority of users install without ever checking a sig. I know it is not trivial to improve this and have no solution. Having some github repo with the sigs helps experts supervise the hosted files and I guess there is a bunch of people supervising all kind of hostings but the doubt – mine and the doubt of others – is a problem when it comes to getting updates spread fast.

It's good to learn that binaries are bit-reproducible. This is essential to trust any binary.
staff
Activity: 4172
Merit: 8419
could anyone loose coins as a result of the bugs fixed in this release?

No. The whole network could be shut down, but the coins would stay put.

Quote
My other question: To have multiple people confirm the quality of a binary, can they compile it separately, getting the same binary? I would love to see as many people that review code to sign the binaries to gain trust. The source being trustful and the binary being signed by just one person is kind of a joke with the money at stake. No offense, Gavin, you are doing a great job and it's maybe a lack of tools or maybe a lack of understanding on my side (which would be a lack of easy and well known tools) but I think this update process needs more trust.
Uhhh.

Our binaries are bit-reproducible, and are always authenticated by multiple parties before being posted: https://github.com/bitcoin/gitian.sigs

We are innovators in this space, your criticism here is really misplaced.
Pages:
Jump to: