[XMR] Monero - A secure, private, untraceable cryptocurrency

[otila]

Just to correct this - we're NOT going to be using the CN tree_hash.c change, because as you pointed out it's not entirely correct. Our correctly patched tree_hash.c is here: https://github.com/rfree2monero/bitmonero/blob/pr-fix-treehash2/src/crypto/tree-hash.c

well, you get integer overflow due to incorrect range check for cnt:

Code:

    size_t ints_size = cnt * HASH_SIZE;

Check rather that cnt <= SIZE_MAX/HASH_SIZE

Anyways, it does not help because you use alloca(), you probably have 8 MiB stack size limit on Linux.

tree_hash_cnt could be simplified, I have

Code:

    size_t cnt = (size_t)1 << __fls(count - 1);

(__fls from Linux source code)

[papa_lazzarou]

lol. Is that like a $5 USD bounty?

2.5 XMR Bounty to create AWS Linux AMI to mine XMR on CPU and GPU http://bitcointalk.org/index.php?topic=771091.msg8695669#msg8695669

Yeah, thanks for doing the math on that one. You get an ass hat for that.

Dude, right now its not profitable. You are better of buying XMR with the money you'll spend on AWS.

[coins101]

Some questions tied to speculative thoughts on the attack.

When the network was spammed to try and bloat the block chain, was that actually part of the attack? Wouldn't you want to slow down the network and cause some transaction volume to slow as part of the prep work?

Maybe if you were trying to take control, a slower network, down to what you could manage, would be a necessity.

To counter the block chain spamming, was the fork to increase the fees an anticipated outcome for the attacker and something he was relying on, or was that a problem that required him to force another fork?

Although the events were some weeks apart, it is still quite a lot of attack activity in a relatively short period of time.

Happy to delete this post if you think it just promotes unnecessary FUD.

[smooth]

Some questions tied to speculative thoughts on the attack.

When the network was spammed to try and bloat the block chain, was that actually part of the attack? Wouldn't you want to slow down the network and cause some transaction volume to slow as part of the prep work?

Maybe if you were trying to take control, a slower network, down to what you could manage, would be a necessity.

To counter the block chain spamming, was the fork to increase the fees an anticipated outcome for the attacker and something he was relying on, or was that a problem that required him to force another fork?

Although the events were some weeks apart, it is still quite a lot of attack activity in a relatively short period of time.

Happy to delete this post if you think it just promotes unnecessary FUD.

Let's address all this after we are done with recovery and have official builds up.

[OrientA]

Some questions tied to speculative thoughts on the attack.

When the network was spammed to try and bloat the block chain, was that actually part of the attack? Wouldn't you want to slow down the network and cause some transaction volume to slow as part of the prep work?

Maybe if you were trying to take control, a slower network, down to what you could manage, would be a necessity.

To counter the block chain spamming, was the fork to increase the fees an anticipated outcome for the attacker and something he was relying on, or was that a problem that required him to force another fork?

Although the events were some weeks apart, it is still quite a lot of attack activity in a relatively short period of time.

Happy to delete this post if you think it just promotes unnecessary FUD.

I have the similar thought

[goofy73]

I have a problem with bitmonerod, here is log:

2014-Sep-06 13:52:18.139976 Starting...
2014-Sep-06 13:52:18.189979 bitmonero v0.8.8.2(0.1-g1b8a68f)
2014-Sep-06 13:52:18.223980 Module folder: F:\monero.win.x64.experimental.0526\bitmonerod.exe
2014-Sep-06 13:52:18.259983 Initializing p2p server...
2014-Sep-06 13:52:18.318986 ERROR c:\temp\monero\new\bitmonero-master-x64\src\p2p\net_node.inl:108 Exception at [node_server::init_config], what=input stream error
2014-Sep-06 13:52:18.318986 ERROR c:\temp\monero\new\bitmonero-master-x64\src\p2p\net_node.inl:239 Failed to init config.
2014-Sep-06 13:52:18.318986 ERROR ..\..\src\daemon\daemon.cpp:174 Failed to initialize p2p server.
2014-Sep-06 13:52:18.345987 Mining has been stopped, 0 finished

Before ive cleared my temp directory

[brownmon]

What's the status of XMR's collaboration with i2p?

[akula999]

anyone having issues with extremehash.com pool?
Close to 3 XMR sitting in pending and growing.

[MTJ151]

Still can't sync   It's been a while now... should have been sorted out by now?

[sammy007]

anyone having issues with extremehash.com pool?
Close to 3 XMR sitting in pending and growing.

This is Monero thread. Use #monero-pools @freenode.net or monero mining thread (link in OP). Contact your pool op using support page.

[fluffypony]

What's the status of XMR's collaboration with i2p?

Ongoing, we've formed a working group with i2p, Abscond, i2pd, and Anoncoin, called Privacy Solutions. i2pd is reaching a level of working-ness that should allow us to start integrating it soon. Given the number of moving parts it's extremely hard to put a timeframe on it.

[fluffypony]

Still can't sync   It's been a while now... should have been sorted out by now?

If you're stuck in the dead fork you have to either use a bootstrap blockchain download from us (see OP), or wait for our rollback fix, or try sync up from scratch.

[fluffypony]

I have a problem with bitmonerod, here is log:

2014-Sep-06 13:52:18.139976 Starting...
2014-Sep-06 13:52:18.189979 bitmonero v0.8.8.2(0.1-g1b8a68f)
2014-Sep-06 13:52:18.223980 Module folder: F:\monero.win.x64.experimental.0526\bitmonerod.exe
2014-Sep-06 13:52:18.259983 Initializing p2p server...
2014-Sep-06 13:52:18.318986 ERROR c:\temp\monero\new\bitmonero-master-x64\src\p2p\net_node.inl:108 Exception at [node_server::init_config], what=input stream error
2014-Sep-06 13:52:18.318986 ERROR c:\temp\monero\new\bitmonero-master-x64\src\p2p\net_node.inl:239 Failed to init config.
2014-Sep-06 13:52:18.318986 ERROR ..\..\src\daemon\daemon.cpp:174 Failed to initialize p2p server.
2014-Sep-06 13:52:18.345987 Mining has been stopped, 0 finished

Before ive cleared my temp directory

Get the latest binary off the OP and try again

Edit: and delete your p2pstate.bin and poolstate.bin, your p2pstate.bin is definitely corrupt.

[Jungian]

What's the status of XMR's collaboration with i2p?

Ongoing, we've formed a working group with i2p, Abscond, i2pd, and Anoncoin, called Privacy Solutions. i2pd is reaching a level of working-ness that should allow us to start integrating it soon. Given the number of moving parts it's extremely hard to put a timeframe on it.

If we are talking in the broadest sense. Are we talking this year?

[krawallmining]

Interesting how stable the prize is, considering the delays.

[fluffypony]

What's the status of XMR's collaboration with i2p?

Ongoing, we've formed a working group with i2p, Abscond, i2pd, and Anoncoin, called Privacy Solutions. i2pd is reaching a level of working-ness that should allow us to start integrating it soon. Given the number of moving parts it's extremely hard to put a timeframe on it.

If we are talking in the broadest sense. Are we talking this year?

I would imagine so, yes - I'm running i2pd in its current form to connect to irc2p, and now that most of the memory leaks have been squashed it's quite stable. There's still a lot of work to be done (the "moving parts" I mentioned), but it's way, way further ahead than when we first partnered up with i2p:)

[matrix961]

Interesting how stable the prize is, considering the delays.

I believe this to be the increased confidence in the devs. They have shown to be consistent in their delivery and extremely fast in reacting to any major issues. They have remained professional and to investors this is a huge plus. There are other factors but for me this is one of the coins I hold without worry.

[krawallmining]

Another reason may be that the still lasting issues hardly effect daytrading at exchanges.

[fluffypony]

Ok - Windows blockchain has been updated with one that is synced up past the fork correctly -

http://monero.cc/downloads/blockchain/win/blockchain.bin
sha: 8c23da70c1291a61444090d8d5127dd6c12efa81

We won't update that blockchain for a few days, although when it updates once the patch is fully tested and deployed that sha will obviously change:)

Thanks for your patience!

[coins101]

Still can't sync   It's been a while now... should have been sorted out by now?

If you're stuck in the dead fork you have to either use a bootstrap blockchain download from us (see OP), or wait for our rollback fix, or try sync up from scratch.

I thought a rollback was the most secure way to remove the rouge blocks and fix the ongoing corruption.

Is that the best of a worst bunch of options? It does come with some risks.