Bitcoin-Qt / bitcoind May15 backport versions (0.7.3, etc) release candidate 3

[Luke-Jr]

With the May 15 changes right around the corner, please help test some of the stable maintenance versions

These are bugfix-only releases, including minimal compatibility updating for the May 15 changes.

Please report bugs by replying to this forum thread.

bitcoind and Bitcoin-Qt version 0.7.3 release candidate 3 (sigs) are now available for download:

• Linux: tar.gz
• Windows: installer | zip
• Source: tar.gz | git

bitcoind and Bitcoin-Qt version 0.6.5 release candidate 3 (sigs) are now available for download:

• Linux: tar.gz
• Windows: installer | zip
• Source: tar.gz | git

bitcoind and Bitcoin-Qt version 0.5.8 release candidate 3 (sigs) are now available for download:

• Linux: tar.gz
• Windows: installer | zip
• Source: tar.gz | git

bitcoind version 0.4.9 release candidate 3 (sigs) is now available for download:

• Please note: The wxBitcoin GUI client is no longer maintained nor supported; CVE-2012-4682 and CVE-2012-4683 are not fixed in 0.4.x since it does not have any anti-DoS system at all. If you want to be secure against this class of DoS attacks (network flooding of invalid data to verify), upgrade to a newer version!
• Linux: tar.gz
• Windows: installer | zip
• Source: tar.gz | git

See git for full changelog

Backport end-of-life (EOL) schedule:

• 0.4.x - EOL by 2013-11-21 (2 years after 0.5.0 released)
• 0.5.x - EOL by 2013-03-30 (1 year after 0.6.0 released)
• 0.6.0.x - EOL now: 0.6.0.x is no longer supported
• 0.6.x - EOL by 2013-11-21 (over 1 year after 0.7.0 released)
• 0.7.x - EOL by 2014-02-18 (1 year after 0.8.0 released)
• 0.8.x - Long-Term Support (LTS): 2-3 years after 0.9.0 released

These are not guarantees. If you need me to maintain any branch longer, please let me know ASAP.

[charleshoskinson]

Luke did I miss something? Are you hard forking?

[Luke-Jr]

Luke did I miss something? Are you hard forking?

A hardfork has been scheduled for May 15, for over a month now...

I've updated the language in the opening post to use the same "changes" terminology.

[charleshoskinson]

Ah thanks. There's been a lot of forking around lately

[toffoo]

No Mac binary releases?

This is particularly unfortunate to not see a Mac v0.7.3 backport because many have found the v0.8.x Mac binaries not-quite-ready-for-primetime and have downgraded to v0.7.2.

If a Mac backport v0.7.3 binary isn't released before the 15th, should we be okay with running v0.7.2 and applying this workaround fix?

http://bitcoin.org/may15.html#workaround

[Luke-Jr]

No Mac binary releases?

This is particularly unfortunate to not see a Mac v0.7.3 backport because many have found the v0.8.x Mac binaries not-quite-ready-for-primetime and have downgraded to v0.7.2.

Gavin does all the Mac stuff, and he's too busy to get involved in backports.
Did you try 0.8.2rc1? If that doesn't work, I'd definitely open an issue (or follow up on an existing one) on GitHub...

If a Mac backport v0.7.3 binary isn't released before the 15th, should we be okay with running v0.7.2 and applying this workaround fix?

http://bitcoin.org/may15.html#workaround

Yes, that should be fine.
Do note, however, that 0.7.2 remains affected by two privacy vulnerabilities: CVE-2013-2272 and CVE-2013-2273