45
[SOLVED] What do I do for this? (thelemmy.club)
submitted 9 months ago* (last edited 9 months ago) by to c/archlinux@lemmy.ml
23 comments fedilink hide all child comments
 

Just installed updates from Pacman, not even touching the AUR. Now when I reboot machine, this happens. It just reboots itself and the cycle repeats itself. Any solutions?

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 9 months ago* (3 children)

You are confusing "what it should do" with "what it does". Vendors are trying to save money like everyone else and will regularly provide defective hardware or software implementations that were never properly tested for any actual functionality beyond said "MS marketing gimmick"

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 9 months ago (2 children)

    It works on my Linux install. Will halt boot if kernal changes or nvidia driver changes and you have not approved the mee keys.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 9 months ago (1 child)

    "It works on my system" vs. "I bricked my device because the basic functionality to replace the pre-installed keys was broken or some idiot vendor had signed his hardware with that MS key" is still bad, even when it runs for the vast majority only using their system with pre-installed keys (those are not actually the ones needing the security and it really is just a marketing gimmick) while just a small minority aiming for security gets screwed by shitty implementations.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 9 months ago

    The intent makes sense, it is a trust chain to ensure the system will only boot if it is not tempered with. We have it on android also, to prevent malicious Kernel and OS changes. Microsoft holding the keys signing is the shit part.

  • permalink
  • fedilink
  • source
  • parent