11
12

UNDER ATTACK / FLAW: Ethereum ETH (self.EthereumClassic)

keepdoing2 が 投稿

Several reports, conflicting reports of issues with GETH. Currently looks like this is only issue for ETH, Their price got hammered down again, 3rd time they have failed to capitalize on the Devcon hype.

https://www.reddit.com/r/ethereum/comments/53dlwl/ethermine_currently_under_dos_attack/

https://www.reddit.com/r/ethereum/comments/53dfof/geth_crashing_memory_leak/

EDITS:

1) Security Alert Issued by Ethereum Foundation

https://blog.ethereum.org/2016/09/18/security-alert-geth-nodes-crash-due-memory-bug/

2) FIX RELEASED Fix for issue can be found here. https://github.com/ethereum/go-ethereum/pull/3006https://github.com/ethereum/go-ethereum/pull/3006 / Miko (ETC Core Dev) is updating it to ETC Geth as we speak. / Note: thanks to ChuckSRQ and the Devs for keeping on top of this!

... ...

SUMMARY: This was an intentional attack on ETH. Messages placed in the attack contracts included terms.... "Go Home" and "with love from Shanghai". It looks like it is over, but it has most likely changed the tone of Devcon. Also, some indications are that this might have originated from addresses linked to DAO Attacker. If this is the case, this isn't about the money.... its someone(s) with clear bad intentions to "ETH"ereum.

全 39 件のコメント
並べ替え:
ベスト (提案されたアイデア)
トップ新着論争中古い順Q&A

[–]ChuckSRQ [スコア非表示]  (10子コメント)

It's a bug in Geth. Possibly a contract that makes calls over and over again. Or some type of memory leak. ETC Developers are looking into it and what should be done on the ETC chain also if anything. Will report back when I have more.

https://github.com/ethereum/go-ethereum/issues/3002

EDIT: Fix for issue can be found here. https://github.com/ethereum/go-ethereum/pull/3006https://github.com/ethereum/go-ethereum/pull/3006

Miko (ETC Core Dev) is updating it to ETC Geth as we speak.

[–]keepdoing2[S] [スコア非表示]  (9子コメント)

Thanks Chuck! PS.... you guys killed it this morning on the podcast! Funny - I was just loading up some big orders to buy ETC just because of how well you did, and noticed price going up - that is when I researrched and saw the ETH problems. Wierd timing. I'm tempted to feel sorry for them. Right before Devcon - this is going to change the tone of the conversations and mood to that whole conference. I am now loading up on ETC.

[–]Hiphopsince1988 [スコア非表示]  (0子コメント)

Lol nope luckily fix was implemented before the conference even started..

[–]ChuckSRQ [スコア非表示]  (5子コメント)

Thanks for that! It doesn't sound like it's a huge problem. Some of the more experienced ETC users are expecting a patch for Geth on ETH within the day.

[–]ethereumcharles [スコア非表示]  (4子コメント)

Considering DevCon is going on, it's going to get fixed very quickly. https://www.youtube.com/watch?v=IW7Rqwwth84

[–]keepdoing2[S] [スコア非表示]  (3子コメント)

That happened to me several times in demos back in the 90's. You learn to laugh it off - but it can still kill the deal :) CEO's and Upper Management was notoriously less amused than the engineers :)

BTW - You and Carlos had a great debut this morning. That was one of the best and most informative podcasts I have seen. I was serious when I said I was loading up on more ETC because of it.

[–]ChuckSRQ [スコア非表示]  (2子コメント)

Fix has been released. Read Edit above.

[–]scryptBYredditor for > 1 year, but has low karma [スコア非表示]  (1子コメント)

So, are there ETC pools which have already adopted it? Which ones?

[–]ChuckSRQ [スコア非表示]  (0子コメント)

Sorry. I should say release is incoming. Geth is being updated but has not been released as of yet.

[–]CarloVetc [スコア非表示]  (1子コメント)

Thanks for the kind words keepdoing. Please let me know anything you think I need to work on for future broadcasts. I'm always looking for ways to improve, I don't take critisim harshly.

[–]keepdoing2[S] [スコア非表示]  (0子コメント)

I actually thought it was as close to perfect as it gets. I am totally serious that everyone interested in ETC should watch that Podcast. You guys covered everything, did it professionally, and even though it was long as hell - I not only watched it all the way through , I was kept interested. And every single bit of misinfo and fud out there was perfectly addressed. I loved it! Off to a great start!

[–]Willidungl [スコア非表示]  (24子コメント)

Does this also affect ETC?

Edit: At first glance it seems to be a memory leak limited to geth, possibly related to this transaction with the german ASCII 'Fahrt nach Hause' meaning 'Go home'

[–]Nichoros_Strategy [スコア非表示]  (11子コメント)

It does if your developers generally just copy ETH's code/clients

[–]Willidungl [スコア非表示]  (10子コメント)

My developers?

[–]DavidDann437 [スコア非表示]  (8子コメント)

Surely everyone has developers in this day and age.. get with the times!

[–]sabbybibiredditor for > 1 year, but has low karma [スコア非表示]  (1子コメント)

even my developers have developers

[–]DavidDann437 [スコア非表示]  (0子コメント)

My developers are in charge of open source projects, leveraging the power of the community to develop for them - potentially allowing me to command 6 billion developers.

[–]Nichoros_Strategy [スコア非表示]  (5子コメント)

If anyone would like to continue this thread please contact my developer. Thank you

[–]DavidDann437 [スコア非表示]  (4子コメント)

I'll have my developer contact your developer and they'll get to work on that.

[–]Bitalik_Vuterinredditor for < 1 week [スコア非表示]  (3子コメント)

Your are developing without a development license!

[–]DavidDann437 [スコア非表示]  (2子コメント)

No developer left behind! that's our policy

[–]CarloVetc [スコア非表示]  (1子コメント)

I didn't have any developers, so I copypasted both of your developers so that now my 2 new developers can coordinate with your developers to develop more developers.

[–]DavidDann437 [スコア非表示]  (0子コメント)

Ah the old copy paste DNA code method, you need to automate it somehow.

[–]Nichoros_Strategy [スコア非表示]  (0子コメント)

their developers*

[–]keepdoing2[S] [スコア非表示]  (11子コメント)

NO. My question to Devs is primarily to see if this COULD down road effect us. This is currently an ETH specific issue with a specific contract transaction that appears to have been an intentional attack. Eth Devs investigating.

The issue seems to be exclusively affecting GETH on the Ethereum Chai..

[–]Hiphopsince1988 [スコア非表示]  (0子コメント)

First off, it DOES effect both and once the code was released you guys were quick to ctrl-c ctrl-v.

[–]Willidungl [スコア非表示]  (7子コメント)

The current main classic full node client is based on geth, right?

[–]ChuckSRQ [スコア非表示]  (6子コメント)

Yes but ETC Devs didnt just copy and paste everything. They made bug fixes on their own when porting over.

[–]RandomRealityChick [スコア非表示]  (0子コメント)

What bug fixes did they make?

[–]keepdoing2[S] [スコア非表示]  (4子コメント)

Everyone should watch the podcast from this morning..... that was one of the primary focuses that it is clear is drilled into this community... SECURITY FIRST. Even in the early days Gravity was talking about concerns with Mist/Geth.

[–]DavidDann437 [スコア非表示]  (0子コメント)

Possibly anything. Glad that's clarified things.

[–]lagaiphone [スコア非表示]  (2子コメント)

Yes, it is a DOS attack!