I am about to install @Arch Linux on a new laptop. This time I am attempting to look into the #secureBoot properly. Trying to boot #archBoot or manually adding #preloader into the install media fails with secure boot violation error. I understand I should enroll loader hashes into the mok list in the nvram. I can't use EFI shell, hashtool.efi, keytool.efi and similar since at that stage of the boot process there's no accessibility support and I can't handle that on my own with OCR snapshots of the laptop screen. Am I missunderstanding the secure boot concept or is that yet another thing I can't overcome no matter how much I am trying to prepare for the task? Of course windows is booting and I do have a screen reader running. But I can't find windows tools capable of manipulating EFI variables. #secureBoot #fail #Accessibility