• Responsabilidade
    26•10 months ago

    This shit again… I moved to LTS kernel exactly because of this bug and now it reached LTS kernel as well…

    • @dootEnglish
      12•10 months ago

      I like how it’s readable both in present and past tenses hehe

  • Southern Wolf
    8•10 months 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.

  • @argv_minus_one@beehaw.org
    8•10 months 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.

  • @jungleben@infosec.pub
    5•10 months 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.

  • SemperverusEnglish
    3•10 months ago

    Is it still broken even if you have TPM completely shut off in UEFI?

    • @planish@sh.itjust.works
      1•10 months 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.