BTCFalk on nostr

The bug in 4.0.0 is this which was fixed in 4.0.1. It had nothing to do with the entropy bug that already existed in 4.0.0 // 4.0.0 bool ckcc_vcp_enabled = true; // 4.0.1 bool ckcc_vcp_enabled; // ...

BTCFalk @BTCFalk 1785935299

According to CCs security advisory the "current" entropy bug exists from 4.0.1 on

So basically they fixed the chcc bug present in 4.0.0 but introduced de TRNG bug 🙈🙈

This is exactly the situation why I opted not to update my CC to the newest version, hot fixes are risky business

@ODELL you have any additional info on this?!

@HODL spread?

11❤️1🤙3🚀1

. · 3w

nostr:nevent1qqs8c2scnp5lqqle504htfltw8qvmkhm7lsc6l9qcxj3c7nevqfz9zqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7q3qak68qfcjj7k95c0jwleu69x72nr8adwv6g80pkwl9xlps6zmkqzqxpqqqqqqzt244hn

jaycrow · 3w

If they say from 4.0.1 onwards it's because 4.0.0 was never officially released. "Version 4.0.0 was built, signed, and tested internally, but its binary was never released publicly. The contemporaneous signing manifest records that internal build and does not indicate public distribution. Firmware...

Big Barry Bitcoin · 3w

My understanding is the bug was introduced in 4.0.0 The confusion comes from the fact that since they patched a bug in that version, they removed it from the list of releases instead of keeping it and adding a "THIS IS A VULNERABLE VERSION" disclaimer. Therefore people see that the first version r...