比特币橙子Trader
@oragnes
BTC Holder & Crypto Research
AI · Tech · Finance · Embodied AI
| TG @chengzi_95330
6.6K Following 75.1K Followers
we hacked ledger.
the @OneKey_Anzen team has successfully reproduced a transaction replacement attack against ledger ethereum app 1.22.1 in our lab.
the bug is a race condition between the transaction display logic and the underlying transaction buffer.
an attacker can overwrite the transaction waiting to be signed while the user is still reviewing a legitimate one.
in simple terms:
- you see transaction a on your ledger.
- you approve transaction a.
- your ledger can end up signing transaction b.
- and you never see transaction b.
to reproduce this, we built the 1.22.1 ELF ourselves, fixed the speculos reset 502 issue, and got the full attack flow working end to end.
ledger fixed this in ethereum app 1.22.3.
if you’re still on an older version, update it.
Show more
Luke = incompetent + malicious.
tl;dr: @lukedashjr decided to use a testnet4 block hash as the random beacon to pick BIP-110-chain's new PoW function.
An absolutely batshit decision. It's clearly possible to manipulate that by just mining blocks with the right hash. Mining a testnet4 block has a trivial cost. So mining one with a specific last byte in the block hash – thus forcing a particular PoW choice – also has a trivial cost.
When Zcash did something similar for a trusted setup, they picked a Bitcoin block in the future, and they specified that the block hash would in turn be re-hashed 2⁴² times¹ to ensure that absolutely no-one could possibly pick the value in advance (that's a 2-3 weeks of sequential computation).
There's two possibilities here:
1) Luke is incompetent.
2) Luke is malicious, and is trying to pick a specific PoW.
The possibilities are not exclusive.
1)
Show more
