*** ALERT *** Upgrade to 0.3.6

[satoshi]

Please upgrade to 0.3.6 ASAP!  We fixed an implementation bug where it was possible that bogus transactions could be displayed as accepted.  Do not accept Bitcoin transactions as payment until you upgrade to version 0.3.6!

If you can't upgrade to 0.3.6 right away, it's best to shut down your Bitcoin node until you do.

Also in 0.3.6, faster hashing:
- midstate cache optimisation thanks to tcatm
- Crypto++ ASM SHA-256 thanks to BlackEye
Total generating speedup 2.4x faster.

Download:
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.6/

Windows and Linux users: if you got 0.3.5 you still need to upgrade to 0.3.6.

[Olipro]

is this in the SVN?

[knightmb]

I appreciate the quickness of this security update, but unfortunately none of the Linux builds work (32bit or 64 bit) because the file is missing. I'm assuming if I go find the file it will work, not sure what luck others will have though using the new build.

Error

Code:

./bitcoin: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

[andy_3_913]

are satoshi and Olipro working together?
if not, any chance you could?

i'm well pleased with the speed enhancements Olipro is making, but i would like bc to be secure!

[jgarzik]

Please upgrade to 0.3.5 ASAP!  We fixed an implementation bug where it was possible that bogus transactions could be accepted.  Do not accept Bitcoin transactions as payment until you upgrade to version 0.3.5!

Like Olipro, got a lot of people doing custom builds out there -- in fact, I must use a custom build on several machines.

May we assume SVN has all necessary updates?

[knightmb]

are satoshi and Olipro working together?
if not, any chance you could?

i'm well pleased with the speed enhancements Olipro is making, but i would like bc to be secure!

So far, the new build (stock) has given a 100% speed increase on my Celeron Machines that couldn't run those custom builds before. I'll compare the new release to the older *optimized* builds to see what the speed difference is just out of curiosity. 

[Bitquux]

are satoshi and Olipro working together?
if not, any chance you could?

i'm well pleased with the speed enhancements Olipro is making, but i would like bc to be secure!

So far, the new build (stock) has given a 100% speed increase on my Celeron Machines that couldn't run those custom builds before. I'll compare the new release to the older *optimized* builds to see what the speed difference is just out of curiosity. 

So far I'm seeing a comparable hashing rate to the most recent of the Olipro 32-bit binaries. It might even be slightly faster.

[jgarzik]

With the official Linux-64bit build, run on Fedora 13, I see it failing badly:

Code:

************************
EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
bitcoin in AppInit()       



************************
EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
bitcoin in CMyApp::OnUnhandledException()       

terminate called after throwing an instance of 'DbRunRecoveryException'
  what():  DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery

Praying my bitcoins aren't eaten...

[knightmb]

With the official Linux-64bit build, run on Fedora 13, I see it failing badly:

Code:

************************
EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
bitcoin in AppInit()       



************************
EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
bitcoin in CMyApp::OnUnhandledException()       

terminate called after throwing an instance of 'DbRunRecoveryException'
  what():  DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery

Praying my bitcoins aren't eaten...

I think you'll be ok, it blew up on me too. Run the older version, you should still see all your coins. Backup first for the next Linux release 

[jgarzik]

With the official Linux-64bit build, run on Fedora 13, I see it failing badly:

Same result on another machine.  BDB errors, and death.  0.3.5 on 64bit Linux is questionable.  You didn't mix up the builds with 32-bit Linux, did you?

debug.log says:

Code:

Bitcoin version 0.3.5 beta
Default data directory /g/g/.bitcoin
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=/garz/bitcoin/data/database strErrorFile=/garz/bitcoin/data/db.log


************************
EXCEPTION: 22DbRunRecoveryException       
DbEnv::open: DB_RUNRECOVERY: Fatal error, run database recovery       
bitcoin in AppInit()       

[jgarzik]

I think you'll be ok, it blew up on me too. Run the older version, you should still see all your coins. Backup first for the next Linux release 

Double-ACK

older version (SVN 117 + listtransactions + getinfo KHPS) works fine, all bitcoins there.  And yes, I should back up before following "please upgrade" instructions...  

[knightmb]

Can windows users upgrade to the 3.5 for now?

Yes, I've tested on Windows XP, 2003, and 7 all went through just fine. You'll enjoy the speed increase as well.  

[err, wait I guess, new version about to spawn]

[satoshi]

Haven't had time to update the SVN yet.  Wait for 0.3.6, I'm building it now.  You can shut down your node in the meantime.  

[satoshi]

SVN is updated with version 0.3.6.

Uploading Windows build of 0.3.6 to Sourceforge now, then will rebuild linux.

[RudeDude]

Ha! One of the changes in there is updated some v "0.3.3" stuff to "0.3.6" but that isn't the important part of the update. :-)

[jgarzik]

SVN r119 seems to work fine here.  No BDB explosion.

[knightmb]

Tested the Windows build across XP, 2003, Vista, 7 (both 32 and 64bit builds), no issues installing or running client. So far so good, looking forward to the Linux client. 

[satoshi]

0.3.6 Linux build is back to the old makefile.unix.  It static links libjpeg so that shouldn't be a problem.

Is that working better?

If you got 22DbRunRecoveryException and you've used someone else's build before, you may need to delete (or move the files somewhere else) database/log.000000*

Windows and Linux users: if you got 0.3.5 you still need to upgrade to 0.3.6.

[knightmb]

Still a no go on the Linux build though, this is the console error I get. I checked to make sure the file was there, but the versions don't match I guess?

64bit Client Error, will try out 32bit client and see if the error is similar.

Code:

./bitcoin: /lib64/libc.so.6: version `GLIBC_2.11' not found (required by ./bitcoin)

The machine I tested this on uses nothing but the stock builds, no modified builds were used prior.

Same error for 32bit client

Code:

./bitcoin: /lib/libc.so.6: version `GLIBC_2.11' not found (required by ./bitcoin)

Linux - Mandriva 2010.0 [64bit and 32bit] OS systems setup

[bitcoinex]

0.3.6 binaries for linux works fine on two my machines (64 and 32 bits) with Debian squeeze/sid