• 0 Posts
  • 171 Comments
Joined 2 years ago
cake
Cake day: April 13th, 2024

help-circle








  • That’s for MBR partitioned disks, where they fight over the first sector of the disk which is used as the boot sector.

    Computer models starting from around 2013 should support UEFI boot. If you boot in UEFI mode you use a GPT partitioned disk with an EFI System Partition. In there Windows does not overwrite grub. In mine for example grub was in the ESP under /EFI/fedora/ and Microsoft found the ESP and put its stuff in /EFI/Microsoft.

    The worst I’ve experienced is that Windows puts the Windows Boot Manager back on top of the UEFI boot order, to fix that, I wrote a comment before, that I’ll just link here, if it’s really just the order you can also just change it back in the UEFI menu.

    Another bad thing is that some laptop UEFIs, especially early ones are utterly broken. They ignore your boot order, or your entries in the UEFI boot manager, sometimes they just load the fallback path defined in the UEFI spec, which is \EFI\Boot\BOOTX64.efi, but that’s the OEMs fault. I’ve seen both Fedora and Microsoft write their loader to the fallback path. I’m not sure if they clobber the other ones if it exists already, because I never boot from that path, so I wouldn’t notice.







  • Her left handed dad - who grew up in a country which had no left handed things - wasn’t able to use the scissors.

    That’s interesting to me. I’m a lefty who’s used to both types of scissors. That means I know how I need to pull sideways with the knuckle of my thumb in the right handed ones so they still cut well. But with the left handed ones I feel like I’m doing way less, I just pull and push up and down without needing the additional deliberate sideways pressure.






  • Yeah agreed especially further down when it’s just randomly rehashing old history. It’s also mixing up decryption and verification even in the beginning of the article. First they write:

    BootROM (Level 0): The CPU runs code burned into it at the factory. This code is immutable (cannot be changed). It uses the ROM Keys to verify the signature of the next loader.

    Then just two paragraphs below:

    The ROM Keys change everything. With these keys, hackers can decrypt the Level 1 Bootloader.

    So which is it? Usually bootloaders in a chain hash the next stage. That hash is compared with the signed hash the stage presents, and the signature on the signed hash is cryptographically verified against the locally stored trusted keys. No encryption or decryption takes place. Maybe this is different for the PS5 but then that would be noteworthy, not something you just assume readers to know.