News for hackers. Stuff that matters.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by pstrateman on Monday May 03, 2021 @01:23AM (#27021887)
The SHA-256 hashes are gpg signed with the key at https://bitcoin.org/laanwj-releases.asc

Nobody actually checks the executable signatures, they're buried in the file properties.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by garmaine on Monday May 03, 2021 @04:53AM (#27022909)
Everyone on macOS and Windows checks the executable signatures automatically on first run.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by ddtaylor on Monday May 03, 2021 @07:08AM (#27023625)
Can't an attacker modify the executable to not do that?
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by freeone3000 on Monday May 03, 2021 @07:16AM (#27023667)
No, because the check isn't part of the executable, it's part of the operating system. An attacker would have to modify the executable to have a valid certificate, which would take several months and a few hundred dollars, which usually makes it not worth it.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by tinus_hn on Monday May 03, 2021 @12:46PM (#27027349)
The alternative is signing it with another certificate which is about $100
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by freeone3000 on Monday May 03, 2021 @01:13PM (#27027788)
From who? It can't be a non-EV cert, since those are trusted less and present the same dialog. A 1-year from Verisign is $500. Comodo is $229. Setigo is $329. All of them require verification that you own a business, which is another $50 to set up an LLC, and the issuance lead time for both of these providers are a few months.

If you have a quick, trusted way of getting an EV code-signing cert trusted by SmartScreen, please, let me know.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by tinus_hn on Monday May 03, 2021 @02:26PM (#27028836)
They do present a dialog but not the same one you get with no or an invalid signature.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by h_anna_h on Monday May 03, 2021 @09:04AM (#27024512)
Signing the hashes instead of the executable leaves you open to collision attacks.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by gojomo on Monday May 03, 2021 @09:19AM (#27024680)
Are you aware of any practical SHA-256 collision attacks?

What do you expect the results would be, if within the next few days it were discovered that there were two different files, with the same SHA-256, each claiming to be the Bitcoin-0.21.1 release?

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by nullc on Tuesday May 04, 2021 @12:03AM (#27033945)
If you know a sha256 collision the bitcoin network will currently pay you about 0.476 BTC (~about $26k USD right now) to publish it.

https://blockstream.info/address/35Snmmy3uhaer2gTboc81ayCip4...

https://blockstream.info/address/39VXyuoc6SXYKp9TcAhoiN1mb4n...

https://blockstream.info/address/3DUQQvz4t57Jy7jxE86kyFcNpKt...

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by drexlspivey on Tuesday May 04, 2021 @07:08AM (#27036243)
In practice, if you try to claim those coins by broadcasting a transaction with the collision the most likely outcome is someone will snatch the coins by changing the output address with his own address (since the scripts contains no signature checking). You would have to give your tx straight to a miner (and hope for the best)
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by gojomo on Wednesday May 05, 2021 @10:48PM (#27058620)
But also, in practice, the fame of announcing such a discovery (with or without an explanation of the method for creating it) could be worth more than $26k.

And if you wanted to profit from it, via submitting the transaction or not, you could likely make far more by speculating on the effects of that announced collision on the Bitcoin price – likely sharply negative.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by gliptic on Monday May 03, 2021 @09:39AM (#27024929)
There's no such thing as "signing the executable". It's always signing a hash.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by h_anna_h on Monday May 03, 2021 @10:51AM (#27025781)
Certain signing algorithms such as ed25519 do not depend on the collision resistance of the hash function when signing the message. They do however when signing the hash.

"It's always signing a hash.", sure, but S(m) and S(h(m)) is a different operation with very different properties.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by littlestymaar on Monday May 03, 2021 @10:31AM (#27025541)
You realize that if SHA-256 collision where something even remotely practical, then the entire bitcoin protocol is instantly dead?
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by h_anna_h on Monday May 03, 2021 @10:53AM (#27025803)
No, I do not realize that. Is the security of the bitcoin protocol based on the collision resistance of SHA-256? If so they should try to find a solution around it.
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by littlestymaar on Tuesday May 04, 2021 @09:22AM (#27037276)
Blocks are identified by their hash, so if you can create a collision between two blocks, there's no way for anyone to know which one is the legit one.

Also, inside a block itself, transactions are part of a Merkle Tree[1], so if you can find a SHA-256 collision, you can also create confusion on what transaction where actually included in a given block.

You cannot really “find a solution around it” for two reasons:

1- the bitcoin blockchain is immutable, so the old blocks can't really be rewritten to work with another hashing mechanism. What you could do is reboot the bitcoin blockchain with another hash algorithm, with a Genesis block summarizing the last know state of the bitcoin blockchain. But that would need consensus among the entire bitcoin community, which will never happen because of reason #2

2- Bitcoin miners own millions of dollars of custom hardware designed for SHA-256 generation (mining), there's no way they'll just be like “OK, let's change hash function, I'll throw this useless stuff away and buy new ones”.

[1]: https://en.wikipedia.org/wiki/Merkle_tree

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by nullc on Monday May 03, 2021 @09:27AM (#27024796)
The signature algorithm uses the same hash, so there isn't any meaningful opening there. :)
Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by h_anna_h on Monday May 03, 2021 @10:58AM (#27025874)
There is a reason ed25519 is used instead of ed25519ph :)

PureEdDSA does not break when a hash function without collision resistance is used.

Re:Bitcoin Core: Bitcoin Core 0.21.1 released with Taproot a... by nullc on Monday May 03, 2021 @11:10AM (#27026084)
Doesn't apply to PGP. :)

And the kind of theoretical attack that non-prehashing protects you from requires that you sign an attacker chosen message -- relevant in some applications but kind of contrived.