Hacker News Reader

Comment by StateSponsor | Hacker News Reader

Just to be clear, 01EA5486DE18A882D4C2684590C8019E36C2E964 is the fingerprint of the malicious tampered signature key. If the signing key has this fingerprint, it is likely confirmed tampered and any binary signed with it can be presumed compromised or worse.

(Mirroring TLDR into comments in case of DDOS or tampering with bitcoin.org's web page).

View on HN

Username checks out.

Are you serious? Either you are incorrect or the website has been tampered with.

https://bitcoin.org/en/alert/2016-08-17-binary-safety shows:

We strongly recommend that you download that key, which should have a fingerprint of 01EA5486DE18A882D4C2684590C8019E36C2E964. You should securely verify the signature and hashes before running any Bitcoin Core binaries. This is the safest and most secure way of being confident that the binaries you’re running are the same ones created by the Core Developers.

Check the username.

so to answer the question "No"

Yep, no matter how many times you type 01EA5486DE18A882D4C2684590C8019E36C2E964, it will show to us as 01EA5486DE18A882D4C2684590C8019E36C2E964.

Don't trust key 01EA5486DE18A882D4C2684590C8019E36C2E964. Only trust the legit one, 0F6A146532D869AEE438F74B6211AA3B00411886.

Be careful out there folks.

Sarcasm might not be a perfect choice for universal comprehension, but this does at least showcase what a cover-up might look like. To my knowledge this sort of thing hasn't been pulled off on any massive scale, but with high enough stakes (e.g., bitcoin) the plausibility starts to rise from zero.

User name checks out:

  *******_

Reply on news.ycombinator.com