After a handful of hours of troubleshooting, I found out that my device’s firmware doesn’t support the Secure Boot setup method provided in the wiki. Then, I read through the Arch wiki page about it, as well as the discussion page because I was a little confused.
In the end, it seems to me that it is a lot of trouble. Has anyone managed to use these different methods such as shim or PreLoader? If so, did you have to do anything different from what is presented in the Arch wiki guide?
Do you guys think it’s even worth it? I mean, I don’t use Windows anymore, but the extra layer of protection would be nice anyway. Besides, I could use it to automatically unlock my LUKS encrypted drive, but to be honest I have been considering dropping the encryption.
Secure boot isn’t that secure, it’s just a thing they pulled out from their butts at ms, to mess with the competition and sell hardware. I’ve been turning it off for years. Just keep your system updated and you are 1000% more secure than on windows.
100% correct. Do not use secure Boot, TPM, or CMS all schemes to either lock your hardware to a specific copy of your OS or to block you from installing software that the OS manufacture / creator doesn’t want you to have cause it either competes with their software or it tends to break their system. Unfortunately Microsoft and Apple aren’t the only bad apples on this front, nor are nonLinux OS’s the only guilty ones. Ubuntu based OS’s and Linux Mint have been know to force peeps to rollback certain pieces of software when they’ve released a new OS version.
Years ago Mint pissed me off cause I had just installed it, had the latest SMPlayer version on it (a version I had been waiting for because it had new features I had been waiting for). Mint released a new OS so I installed it and went to set it up only to find I could not install the latest SMPlayer or the most current of some other apps. That screams that there is something wrong with your updated OS and it should of stayed in development longer.
