Comment by TommyTran732
4 hours ago
Because it's true, and I know what he said, I am not confused at all. Did you not read anything at all?
On the Librem laptop, the tampering is done by PureBoot and inject into /run/firmware. The other user was linking the stuff with the laptop.
*On a Librem 5, it is stored on a separate chip, then they read it with the initramfs, then mount it on top of the regular filesystem at /lib/firmware*.
Like I said, it's just shuffling stuff around.
Here is the actual code, if you care enough to read it: https://source.puri.sm/Librem5/librem5-fw-jail/-/blob/pureos...
If you can't read code, here is the marketing material: https://puri.sm/posts/shipping-new-sparklan-wifi-cards-with-...
If you don't know that the firmware for components/peripherals can either be uploaded to them by Linux or just stored on some flash chip on the component, read: https://www.chromium.org/chromium-os/developer-library/refer...
I'm tired of arguing with you. I see no effort from your side to come to some understanding or to clarify anything. Here's why.
> On the Librem laptop, the tampering is done by PureBoot
What do you mean by "tampering" here? Is uploading firmware to peripherals a "tampering"? Why is this a problem, compared with other devices? Does anybof those blobs run on the CPU? I don't understand what you are trying to say.
> If you don't know that the firmware for components/peripherals can either be
I do know. How is this relevant? I never denied that the device does have some proprietary blobs.