2 ms·
Unfortunately "non-free firmware" doesn't really capture the entire issue, akin to how the FSF misses the mark with their baked-into-flash exception. Proprietar
by mindslight 4y ago
Unfortunately "non-free firmware" doesn't really capture the entire issue, akin to how the FSF misses the mark with their baked-into-flash exception. Proprietary binary blob on a device effectively separated by an IOMMU? That's a peripheral, most of them run non-free firmware. Proprietary binary blob on a device that has DMA access? That's a tainted main computer with a security issue.
I hope the installer settles out into making these distinctions and informing users of the compromises being made. When I stick a Debian installer into a machine that requires non-free firmware to work, my intent is pretty clear. But that doesn't apply to someone just starting out.
- no_time 4y ago>Proprietary binary blob on a device effectively separated by an IOMMU? That's a peripheral, most of them run non-free firmware. Proprietary binary blob on a device that has DMA access? That's a tainted main computer with a security issue. I feel like that's a completely reasonable viewpoint to have. For example, MS Pluton bothers me 100x more than my car keys having nonfree, locked firmware. In an ideal world, both of them are open. But in the meantime I'd be content with not having desktop CPU's be controlled and monitored remotely by their manufacturers instead of their owner.
- deleted 4y ago[deleted]