Re: [Bitcoin-development] Another uninitialized memory problem

On Mon, Jun 2, 2014 at 10:01 PM, Toshi Morita wrote: > I'm seeing another uninitialized memory problem in bitcoind using valgrind: Thanks for the report. Which version/commit id of bitcoind? Wladimir -- Learn Graph Dat

Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken

An attack on the mining difficulty algorithm does not imply violation of the typical security properties of a cryptographic hash function*. Assume someone discovers a method which makes it far easier to discover new blocks, this method: may or may not be implementable by the current SHA256 ASIC ha

Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken

On 6/3/2014 12:29 AM, xor wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, > > I thought a lot about the worst case scenario of SHA256d being broken in a way > which could be abused to > A) reduce the work of mining a block by some significant amount > B) reduce the work of mining

Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken

There is a relevant post from Satoshi on this: https://bitcointalk.org/index.php?topic=191.msg1585#msg1585 Quote: "If SHA-256 became completely broken, I think we could come to some agreement about what the honest block chain was before the trouble started, lock that in and continue from there w

Re: [Bitcoin-development] Another uninitialized memory problem

I think I see the problem. On Mon, Jun 2, 2014 at 4:01 PM, Toshi Morita wrote: > I'm seeing another uninitialized memory problem in bitcoind using valgrind: > > tm@tm-VirtualBox:~/bitcoind/bitcoin/src$ valgrind ./bitcoind > ==2337== Memcheck, a memory error detector > ==2337== Copyright (C) 2002

Re: [Bitcoin-development] Another uninitialized memory problem

I looked at this a bit more yesterday, and it looks like both sides of the comparison were uninitialized, and I fixed one side, but the other side has the same problem. I'll try to investigate further this afternoon once I get out of meetings/meetings prep. Toshi On Tue, Jun 3, 2014 at 9:43 AM

Re: [Bitcoin-development] Another uninitialized memory problem

Does this fix it? https://github.com/bitcoin/bitcoin/pull/4282 On Tue, Jun 3, 2014 at 12:47 PM, Toshi Morita wrote: > I looked at this a bit more yesterday, and it looks like both sides of the > comparison were uninitialized, and I fixed one side, but the other side has > the same problem. > >

[Bitcoin-development] # error "Bitcoin cannot be compiled without assertions." <<<

Hello What is the issue with the Bitcoin code for 0.9.x with regard to assertions that isn't in 0.8.6 or previous releases? on April 18th, I offered https://github.com/bc4-old-c-coder/bitcoin/commit/f0d221e56a12947b67b9c8f43cc5832b665052c8 this commit and code with all side effects removed

Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken

Luke Dashjr writes: > On Tuesday, June 03, 2014 4:29:55 AM xor wrote: >> Hi, >> >> I thought a lot about the worst case scenario of SHA256d being broken in a >> way which could be abused to >> A) reduce the work of mining a block by some significant amount >> B) reduce the work of mining a block

Re: [Bitcoin-development] Lets discuss what to do if SHA256d is actually broken

Hey Rusty, This is intriguing, do you have a writeup somewhere I can read more about ? Thanks, Charlie CharlieShrem.com | *Please **encrypt messages with my PGP key * On Tue, Jun 3, 2014 at 8:45 AM, Rusty Russell wrote: > Luke Dashjr writes: > > On Tuesday

[Bitcoin-development] Bitcoin Core 0.9.2 release candidate 1 is available

Bitcoin Core version 0.9.2rc1 is now available from: https://bitcoin.org/bin/0.9.2/test This is a release candidate for a new minor version release, bringing mostly bug fixes and some minor improvements. Release candidates are wide-scale testing releases, so use with care. Non-technical users m