Here's the root error I believe: https://github.com/paritytech/parity/blob/master/js/src/cont... The initWallet function should have been marked internal, but was instead not marked. Unmarked functions default to public in Solidity, so anyone can call that function and reinitialize the wallet to be under their control
153k Ether Stolen in Parity Multi-Sig Attack
51–60 of 754 posts
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#52If you were the attacker and you now have the ETH in your wallet, how do you cash out without anyone identifying you and maximising your profits?
Also has the attacker broken a law by exploiting a bug in the contract?
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#53Re: 153k Ether Stolen in Parity Multi-Sig Attack
#54https://etherscan.io/address/0x1dba1131000664b884a1ba2384641... -- white hat group exploited the vuln and are holding people's crypto for them.
- Who's the "white hat group"? Why do people have confidence in it?
- Why does everyone believe they'll give back $75M+? If they decided to just keep it, what could anyone do?
- How will people even be able to claim ownership of the ETH in a way that's verifiable so they know they're giving it back to the right person?
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#55Here's the root error I believe: https://github.com/paritytech/parity/blob/master/js/src/cont... The initWallet function should have been marked internal, but was instead not marked. Unmarked functions default to public in Solidity, so anyone can call that function and reinitialize the wallet to be under their control
I can literally feel how Ethereum changes the law. I mean, seriously, no need for lawyers anymore. On ethereum it's is simple: You got fucked, live with it. "Bad faith? It's the code, didn't you read it?"
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#56I've posted this before [0], but it's still apropos regarding the foolishness that is Ethereum. [Ethereum] only makes sense if all of the following obtain: (a) the code is 100% bug-free (b/c accidents cannot be rewound) (b) all code-writers are 100% honest (their code does what they say) (c) all contract participants are 100% perfect code readers (so as to not enter into fraudulent contracts) (Strictly speaking, only…
Not really true. Nothing has to be perfect if there is insurance infrastructure. People should not use contracts they have no reason to trust. As a contract becomes more important it should be viewed/vetted/trusted by as many entities as possible. Users of the contract should pay an insurance fee that goes to the vetters, who promise to reimburse in case of unpredictable behavior. Yes, this means applying some meatsp…
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#57https://etherscan.io/address/0xb3764761e297d6f121e79c32a6582...
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#58I've posted this before [0], but it's still apropos regarding the foolishness that is Ethereum. [Ethereum] only makes sense if all of the following obtain: (a) the code is 100% bug-free (b/c accidents cannot be rewound) (b) all code-writers are 100% honest (their code does what they say) (c) all contract participants are 100% perfect code readers (so as to not enter into fraudulent contracts) (Strictly speaking, only…
The theft wasn't due to an issue in the core protocol of Ethereum, it's due to faulty code in a single piece of software (as you can see throughout the rest of the thread).
It's a matter of poor engineering practices, not a flaw in the fundamentals of the protocol.
If an engineer designed a bridge, and it failed due to a flaw in the design -- say the math on a strut's angle was bad and the bridge collapsed causing millions in damages and took a few lives. Do you blame steel, all steel, and everybody who uses steel in construction as foolhardy? Or do you blame the engineer, the safety inspectors, and the company that oversaw the project?
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#59Here's the root error I believe: https://github.com/paritytech/parity/blob/master/js/src/cont... The initWallet function should have been marked internal, but was instead not marked. Unmarked functions default to public in Solidity, so anyone can call that function and reinitialize the wallet to be under their control
> Unmarked functions default to public in Solidity What kind of brain-dead apes designed this language? This would be a stupid decision in any language, never mind one specifically intended for high-value transactions.
Re: 153k Ether Stolen in Parity Multi-Sig Attack
#60A much more useful explanation: https://press.swarm.city/parity-multisig-wallet-exploit-hits...
What?!? That seems like a pretty relaxed response for someone who just lost 8m dollars.