Bitcoin-Qt, bitcoind version 0.5.2 released

[Luke-Jr]

Bitcoin version 0.5.2 is now available for download at:
  http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.2/

This is a bugfix-only release based on 0.5.1.

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

Stable source code is hosted at Gitorious:
  http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.2#.tar.gz

BUG FIXES

• Check all transactions in blocks after the last checkpoint (0.5.0 and 0.5.1 skipped checking ECDSA signatures during initial blockchain download).
• Cease locking memory used by non-sensitive information (this caused a huge performance hit on some platforms, especially noticable during initial blockchain download; this was
  not a security vulnerability).
• Fixed some address-handling deadlocks (client freezes).
• No longer accept inbound connections over the internet when Bitcoin is being used with Tor (identity leak).
• Re-enable SSL support for the JSON-RPC interface (it was unintentionally disabled for the 0.5.0 and 0.5.1 release Linux binaries).
• Use the correct base transaction fee of 0.0005 BTC for accepting transactions into mined blocks (since 0.4.0, it was incorrectly accepting 0.0001 BTC which was only meant to be relayed).
• Don't show "IP" for transactions which are not necessarily IP transactions.
• Add new DNS seeds (maintained by Pieter Wuille and Luke Dashjr).

Thanks to everybody who contributed code or helped test this release:

Luke Dashjr
Matt Corallo
Wladimir J. van der Laan
Gavin Andresen
Pieter Wuille
Dylan Noblesmith

[1714015537]

1714015537

[Mushoz]

Great job! Well done! Is this the same as the rc1 that you posted earlier (Except for the version number change of course) or has something been changed between this release and rc1? Thanks

[deepceleron]

minimize bug reported on the release-candidate thread...

[hazek]

No PGP signatures?

[Luke-Jr]

Great job! Well done! Is this the same as the rc1 that you posted earlier (Except for the version number change of course) or has something been changed between this release and rc1? Thanks

No changes, but the Windows Bitcoin-Qt was rebuilt by multiple people (devrandom and sipa) to ensure integrity since it isn't 100% deterministic yet.

[Luke-Jr]

minimize bug reported on the release-candidate thread...

Please report to the GitHub issue tracker now.

[Luke-Jr]

No PGP signatures?

http://luke.dashjr.org/programs/bitcoin/files/bitcoin-0.5.2/SHA256SUMS.asc

I presume more to follow shortly. Gitian sigs at https://github.com/bitcoin/gitian.sigs/tree/master/0.5.2

[dooglus]

Which git repository is the v0.5.2 tag in?  I've not been able to find it.

[Luke-Jr]

Which git repository is the v0.5.2 tag in?  I've not been able to find it.

http://gitorious.org/+bitcoin-stable-developers/bitcoin/bitcoind-stable

[dooglus]

Which git repository is the v0.5.2 tag in?  I've not been able to find it.

http://gitorious.org/+bitcoin-stable-developers/bitcoin/bitcoind-stable

Thanks.

git://gitorious.org/+bitcoin-stable-developers/bitcoin/bitcoind-stable.git worked for me.

[dlb76]

updated to 0.5.2-beta
Thanks!

[os2sam]

I installed this version and it worked just fine initially.  But now every time I try to run it I get a DEP violation.  Does this version of the official client really execute code from the stack or other protected data only memory areas?!?!?!?!?
Thanks,
Sam

[Luke-Jr]

I installed this version and it worked just fine initially.  But now every time I try to run it I get a DEP violation.  Does this version of the official client really execute code from the stack or other protected data only memory areas?!?!?!?!?

I'm assuming "DEP violation" is some kind of no-execute thing? AFAIK, no Bitcoin-Qt does this. Since you mention it worked before, I would be concerned that perhaps you've been infected by some kind of virus/trojan. I suggest getting your wallet.dat off that computer ASAP just in case, then looking into it further.

[os2sam]

I installed this version and it worked just fine initially.  But now every time I try to run it I get a DEP violation.  Does this version of the official client really execute code from the stack or other protected data only memory areas?!?!?!?!?

I'm assuming "DEP violation" is some kind of no-execute thing? AFAIK, no Bitcoin-Qt does this. Since you mention it worked before, I would be concerned that perhaps you've been infected by some kind of virus/trojan. I suggest getting your wallet.dat off that computer ASAP just in case, then looking into it further.

Yes DEP is Data Execution Prevention.  Memory can be marked as Data only so that it should be impossible to execute code from an area marked as such.  The stack is the main area that should be read only but many old/legacy apps do execute code from the stack.

I appreciate the assurance that the Bitcoin Client does/should NOT do this, which is what I had suspected and hoped for.

I am currently scanning my system for virus's/malware.  I don't think I've gotten anything on this machine, but hey it is Windoze.
Thanks,
Sam

[os2sam]

I installed this version and it worked just fine initially.  But now every time I try to run it I get a DEP violation.  Does this version of the official client really execute code from the stack or other protected data only memory areas?!?!?!?!?

I'm assuming "DEP violation" is some kind of no-execute thing? AFAIK, no Bitcoin-Qt does this. Since you mention it worked before, I would be concerned that perhaps you've been infected by some kind of virus/trojan. I suggest getting your wallet.dat off that computer ASAP just in case, then looking into it further.

Well I have scanned this system with Security Essentials, MRT, System Sweeper and Windows Defender Offline.

So I don't think it has a virus.

But now after several reboots I can again run the client.  Doesn't exactly give me a warm fuzzy feeling.

By the way, why is it now called Bitcoin-qt?
Sam

[rjk]

I installed this version and it worked just fine initially.  But now every time I try to run it I get a DEP violation.  Does this version of the official client really execute code from the stack or other protected data only memory areas?!?!?!?!?

I'm assuming "DEP violation" is some kind of no-execute thing? AFAIK, no Bitcoin-Qt does this. Since you mention it worked before, I would be concerned that perhaps you've been infected by some kind of virus/trojan. I suggest getting your wallet.dat off that computer ASAP just in case, then looking into it further.

Well I have scanned this system with Security Essentials, MRT, System Sweeper and Windows Defender Offline.

So I don't think it has a virus.

But now after several reboots I can again run the client.  Doesn't exactly give me a warm fuzzy feeling.

By the way, why is it now called Bitcoin-qt?
Sam

Try MalwareBytes.

It is called Bitcoin-qt because the GUI interface was re-written in the QT language by Wumpus.

[Luke-Jr]

Well I have scanned this system with Security Essentials, MRT, System Sweeper and Windows Defender Offline.

So I don't think it has a virus.

But now after several reboots I can again run the client.  Doesn't exactly give me a warm fuzzy feeling.

Perhaps open an issue on GitHub; maybe someone else knows how to debug Windows stuff.

By the way, why is it now called Bitcoin-qt?

The old client (aka wxBitcoin) was replaced with Bitcoin-Qt, which is a complete rewrite of the GUI.

[os2sam]

I installed this version and it worked just fine initially.  But now every time I try to run it I get a DEP violation.  Does this version of the official client really execute code from the stack or other protected data only memory areas?!?!?!?!?

I'm assuming "DEP violation" is some kind of no-execute thing? AFAIK, no Bitcoin-Qt does this. Since you mention it worked before, I would be concerned that perhaps you've been infected by some kind of virus/trojan. I suggest getting your wallet.dat off that computer ASAP just in case, then looking into it further.

Well I have scanned this system with Security Essentials, MRT, System Sweeper and Windows Defender Offline.

So I don't think it has a virus.

But now after several reboots I can again run the client.  Doesn't exactly give me a warm fuzzy feeling.

By the way, why is it now called Bitcoin-qt?
Sam

Try MalwareBytes.

It is called Bitcoin-qt because the GUI interface was re-written in the QT language by Wumpus.

I just scanned again with Malwarebytes.  The only malware it found was CGminer and Ufasoft miner.
Thanks,
Sam

[os2sam]

Well I have scanned this system with Security Essentials, MRT, System Sweeper and Windows Defender Offline.

So I don't think it has a virus.

But now after several reboots I can again run the client.  Doesn't exactly give me a warm fuzzy feeling.

Perhaps open an issue on GitHub; maybe someone else knows how to debug Windows stuff.

If I can get it to reproduce I'll do that.
Thanks,
Sam

[os2sam]

Would it be possible to have a forum topic just for release announcements for the Bitcoin Client software?  It would be nice to have them all in one place.
Just a thought,
Sam