• argv_minus_one@beehaw.org
    112·
    1 year ago

    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.

  • Southern Wolf@pawb.social
    81·
    1 year ago

    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.

  • jungleben@infosec.pub
    5·
    1 year ago

    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.

    • planish@sh.itjust.works
      1·
      1 year ago

      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.

    • exi@feddit.de
      41·
      1 year ago

      You can’t trust any full disk encryption without it because only a TPM can verify that your bootloader and initrd are not compromised.