3 ms·

Okay then I don't get it. What even is the point of secure boot when your entire goal is to run arbitrary kernel mode code? You're effectively always running in

Okay then I don't get it. What even is the point of secure boot when your entire goal is to run arbitrary kernel mode code? You're effectively always running in test-signing mode on Linux -- your entire goal is to be able to run your own modules, which is what test-signing mode does. And if you want to be in that situation, you can permanently enable it with bcdedit; there's no need to constantly toggle it. If your complaint is that you have to cough up $$$ to have your driver be trusted by other users' machines, yeah, I'm happy to rant about that issue, but that's not an issue with the "difficulty" of the process. That's like saying it's hard to use a Lamborghini because it's too expensive. As for the names and patterns... idk, it's hard for me to see what's similar, except that both systems have file systems, both have handles/descriptors, etc... which is hardly an interesting point. Everything from the way you hook I/O to the way syscalls are handled to the quality of the documentation is vastly different on each system.

snagglegaggle 7y ago
> What even is the point of secure boot when your entire goal is to run arbitrary kernel mode code? Err, it's code I wrote, or code I am likely to be familiar with? My issue isn't with the feature of driver signing but its application. I can choose to be in test signing mode on Linux or not, and if I am, it doesn't gimp the system in arbitrary ways. Look again, Windows is like a black box over a rewritten Unix kernel. It's kind of funny. It took a while for it to click.
- mehrdadn 7y ago
  > My issue isn't with the feature of driver signing but its application. I can choose to be in test signing mode on Linux or not, and if I am, it doesn't gimp the system in arbitrary ways. I don't know what "gimp the system in arbitrary ways" means. I've been running Windows in test-signing mode for years with no problem. Microsoft doesn't officially bless it, but that doesn't exactly matter in any material way.

snagglegaggle 7y ago

> What even is the point of secure boot when your entire goal is to run arbitrary kernel mode code? Err, it's code I wrote, or code I am likely to be familiar with? My issue isn't with the feature of driver signing but its application. I can choose to be in test signing mode on Linux or not, and if I am, it doesn't gimp the system in arbitrary ways. Look again, Windows is like a black box over a rewritten Unix kernel. It's kind of funny. It took a while for it to click.

mehrdadn 7y ago
> My issue isn't with the feature of driver signing but its application. I can choose to be in test signing mode on Linux or not, and if I am, it doesn't gimp the system in arbitrary ways. I don't know what "gimp the system in arbitrary ways" means. I've been running Windows in test-signing mode for years with no problem. Microsoft doesn't officially bless it, but that doesn't exactly matter in any material way.