Pages:
Author

Topic: Bitcoin-Qt / bitcoind version 0.8.3 released - page 2. (Read 13409 times)

legendary
Activity: 1596
Merit: 1091
With the block chain growth it would be exceptionally nice to have build in database placement options in the QT. maybe even allow for automatic mirroring, spanning, and automatic wallet/DB backup.

I use -datadir command to place the database on a NAS for security and storage reasons, it's just not that 'slick' of a solution.

The blockchain already has automatically mirroring and spanning; that is fundamentally what the bitcoin client does in the peer-to-peer network.

The wallet is quite small, and you absolutely should be backing that up on a regular basis.

full member
Activity: 224
Merit: 100
With the block chain growth it would be exceptionally nice to have build in database placement options in the QT. maybe even allow for automatic mirroring, spanning, and automatic wallet/DB backup.

I use -datadir command to place the database on a NAS for security and storage reasons, it's just not that 'slick' of a solution.
full member
Activity: 206
Merit: 100
I look forward to the actual release... 1.0.0
hero member
Activity: 826
Merit: 500
Crypto Somnium
Cheers  Cheesy
newbie
Activity: 9
Merit: 0
thank you! Smiley
newbie
Activity: 28
Merit: 0
Way to stay on top of it... Smiley
newbie
Activity: 28
Merit: 0
Thanks guys for update!!  Grin
full member
Activity: 124
Merit: 100
Thank you, dev-team.  Smiley
hero member
Activity: 784
Merit: 501
Thanks for the update. Smiley

Minor remark: I use -datadir as an option to keep my coins in a non standard directory (as an extra security measure against wallet stealers) and when I install a new version it removes the flag in the shortcut. So I have to manually add it again after the update. Would be nice if it was kept by the update.
legendary
Activity: 858
Merit: 1000
Yay! Honestly, I have no idea what that means, but it seems like security fixes, so good job!
sr. member
Activity: 248
Merit: 252
Any idea on if the attack was used or it's impact at the time?

Yes, it was used.  Some lower memory nodes crashed.



Does the fix limit any functionality?

What do you think this means?

"Truncate over-size messages to prevent a memory exhaustion attack."
member
Activity: 98
Merit: 10
For people interesting in the actual code changes, but aren't active developers heres a link.

https://github.com/bitcoin/bitcoin/compare/v0.8.2...v0.8.3
full member
Activity: 238
Merit: 100
Any idea on if the attack was used or it's impact at the time?

Yes, it was used.  Some lower memory nodes crashed.



Does the fix limit any functionality?
full member
Activity: 238
Merit: 100
Love the Bitcoin.
Good work dev team!
sr. member
Activity: 424
Merit: 250
Quick question.

I was running bitcoind on a EC2 micro instance, and it kept crashing. I assumed it was due to low memory. I've since upgraded to a small instance.

Is it possible the crashes were due to these attacks and it can actually run fine on a micro instance?

Can anyone possibly back this up? Or does micro instances simply have too little RAM to feasibly run it? Otherwise going to try and run bitcoind on a micro instance again to see what happens.

Thanks for all the dev work!
legendary
Activity: 2856
Merit: 1518
Bitcoin Legal Tender Countries: 2 of 206
Thank you very much, all!
hero member
Activity: 714
Merit: 500
Are ฿itcoins Radioactive?
Bitcoin-Qt version 0.8.3 is now available from:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.3/

This is a maintenance release to fix a denial-of-service attack that
can cause nodes to crash.

Please report bugs using the issue tracker at github:
  https://github.com/bitcoin/bitcoin/issues

0.8.3 Release notes

Truncate over-size messages to prevent a memory exhaustion attack.

Fix a regression that causes excessive re-writing of the 'peers.dat' file.



Thanks to Peter Todd for responsibly disclosing the vulnerability
( CVE-2013-4627 ) and creating a fix.
Many thanks for this update.
legendary
Activity: 1596
Merit: 1091
Any idea on if the attack was used or it's impact at the time?

Yes, it was used.  Some lower memory nodes crashed.

rme
hero member
Activity: 756
Merit: 504
Good work, Gavin, keep working  Grin
Thanks
hero member
Activity: 994
Merit: 507
Truncate over-size messages to prevent a memory exhaustion attack.

....
Thanks to Peter Todd for responsibly disclosing the vulnerability
( CVE-2013-4627 ) and creating a fix.
Any idea on if the attack was used or it's impact at the time?
Pages:
Jump to: