#Do nvidia proprietary drivers cause issue on systems with secure boot?
1 messages · Page 1 of 1 (latest)
why
I have the same question
I enabled something to do with MOK in my BIOS
But I never enabled secure boot. I don't really know what that's about.
I'm also using nvidia but that's only on 1/4 of my systems
from what i can tell, it just causes weird problems with linux in general
it's not necessarily nvidia related
iirc, what secure boot does is basically just make you verify that whatever you're booting into is safe or whatever, but it basically just doesn't take linux into account at all which is kind of a pain
I don't know what you mean by "it doesn't take linux into account at all"
from the research I've done, secure boot is absolutely worth using and provides a certain degree of security that you can't really achieve with anything else. Coreboot and TPM exist but they're just layers and don't do what secure boot does.
idk from what i've heard, it doesn't add much security and just makes linux a pain. i've in general heard disabling it being a solution to a lot of problems on linux.
this kinda thing is what i mainly hear about secure boot:```
Yes, it is "safe" to disable Secure Boot.
Secure boot is an attempt by Microsoft and BIOS vendors to ensure drivers loaded at boot time have not been tampered with or replaced by "malware" or bad software.
With secure boot enabled only drivers signed with a Microsoft certificate will load. This helps to keep a users computer secure from malicious software being loaded at boot.
I think root kits were the genesis of the secure boot scheme.
That being said - if you are a wise and savvy computer user and surfer of the internets it is unlikely that a malicious driver will find its way into your machine.
honestly in general if you just look up "secure boot bad with linux", you'll see what i mean
in general, just do some research
you "can" use linux with secure boot, and it does have minor benefits, but it is honestly just generally not recommended.