Call me when the FSF isn't actively hurting the cause for hardware freedon by having bass-ackwards certification rules that result in designs where non-free parts are made invisible and untouchable and unfreeable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Tell me a *single* way in which it is better to have some proprietary firmware hidden in some inaccessible Flash memory instead of having that same exact firmware in /lib/firmware. Both included proprietary firmware, but the former deprives me of many more freedoms!
I want the freedom to *reverse engineer* the proprietary firmware, to *audit* the proprietary firmware, to *patch* the proprietary firmware, and ultimately to *replace* the proprietary firmware. The FSF *requires* depriving me of those freedoms to gain certification.
-
-
It also means RYF devices are untrustworthy by default, because their proprietary firmware is unauditable, and therefore its privacy implications cannot be understood. It could have one or multiple backdoors.
-
This Tweet is unavailable.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.