• ulterno
    link
    fedilink
    English
    arrow-up
    0
    ·
    7 hours ago

    Nice to know.

    So, I would assume the firmware gave write access to a part of permanent memory, critical to starting the system.

    I feel like that would be someone like me, thinking of it as a feature and giving the possible values for those variables in the readme. And of course, who reads the readme even though it says “READ ME”?

    • jj4211@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      5 hours ago

      UEFI defines a structured way to have data shared with OS as read write variables, including the ability to create, modify, and delete variables that UEFI can see.

      However, some firmware used this facility to store values and then their code assumed the variables would always be there. The code would then crash when it goes to read a deleted variable and not know what to do. The thing is deleting those variables per spec is a perfectly valid the due the OS to do, but firmware was buggy and the bugs not caught because normally OS would not bother those variables except for a few standard popular ones, like boot order.

      • ulterno
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 hours ago

        I see, in that case, that would not be someone like me :P as I tend to care about specifications.

        This is a really useful explanation for someone who doesn’t know about the UEFI spec.