This shit again... I moved to LTS kernel exactly because of this bug and now it reached LTS kernel as well...
this post was submitted on 19 Aug 2023
117 points (97.6% liked)
Linux
48397 readers
711 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
fixes introduced regressions
Software development in a nut shell
I like how it's readable both in present and past tenses hehe
Good. TPM firmware is a high-value attack surface that, if penetrated, gives the attacker complete and irreversible control over the entire machine. It's also proprietary code and only receives security updates for a small fraction of its service life, so it's most likely riddled with vulnerabilities. It should be disabled, as much as possible, if you at all value the security of your system.
Huh, this might be one of the few examples of "don't break userspace" not being held to by Linus and co? I'm sure stuff like this has happened before, but "don't break userspace" has been a fairly strong guiding principle for the kernel for sometime. So seeing something like this happen is actually a bit surprising.
Though I guess it could be argued that if the removal of fTPM causes fewer bugs/issues than leaving it in place then userspace wasn't broken. But still, it's interesting to see regardless.
I've had fTPM issues with the bios because I changed CPUs and lost key attestation. Maybe it's my fault, but the reset process isn't documented anywhere clearly and it's not worth digging up my old CPU to reset the Mobo.
What's a good usecase for TPM in Linux?
You can't trust any full disk encryption without it because only a TPM can verify that your bootloader and initrd are not compromised.
Measured boot.
Is it still broken even if you have TPM completely shut off in UEFI?
It sound like what's broken is the TPM. So if it is shut off it would be both broken and off, and you might not care about the broken.