The downside is having to pay hundreds of dollars for an EV code signing cert just to submit a driver to Microsoft for Microsoft to sign.
If you're an amateur/hobbyist/tinkerer and just want to play with kernel driver development, then you can disable the signing enforcement.
Anyway I'm sorry for derailing from the actual point of this post - it's a very cool project!
It also means, that we will not get some nice things, we would otherwise have. See also iSCSI initiator or FUSE for macOS. They have same problem - need to be signed by the right certificate, so nobody bothered.
Other systems, when they are running in Secure Boot mode, also accept kernel modules signed by the same keys, that are enrolled into UEFI. Why can't Windows and Mac do the same?
Because of corporate control.
Which ones? Linux certainly isn't made by hobbyists today. It used to be, but that was a very long time ago.
I wasn't aware that FUSE for Mac is signed nowadays. When I was checking it few years ago, it was an issue.
The iSCSI terminator for Mac still has the same issue. The code is on github, making it work is the user problem.
Yeah cool project, yet if you'll read the issues on github, you might realize, that at some point no one will be able to use it hassle free, when the author stops renewing a code signing certificate. And for a hobby project, I wouldn't blame him. Some people can't use it hassle free now, because of signing issues.
I ceratinly can't install it on my gf's notebook, so that she can play audio over my speakers, because it would stop working after each reboot.