So I've spent a good day or two frustratedly googling for how you can develop 64 bit Kernel-Mode drivers in Windows 10 (does not apply to Win8 or earlier), and specifically test in the development environment.
Basically I have a physical harddrive kernel-mode driver that "mounts" a virtual drive like a physical drive and maps the Win32 CreateFile API's to a user mode application that then routes the commands to a remote network on another server (similar to VPN but custom, flexible).
I use this to install and run programs and store files on a remote system so it needs to be an emulated physical drive (Network Attached has too much limitations, and instabilities). - This is similar to SAN, except in a non-corporate network.
So my question(s) are, does anyone else frustrate about Microsoft completely blocking out us developers from kernel mode developing for personal use, when you do not have the economy to buy a certificate.
And what options do I have for running my driver on my Windows 10 computer, without purchased certificates?
There doesn't seem to be any ways to circumvent the new EV certificate system which completely forces you to buy certificate, even if you know what you're doing and you accept the risk of making your system vulnerable.
If you have no knowledge of Windows 10 KMCS driver development, please leave the questions to the experienced, as Windows 8 doesn't require the new EV system.
Microsoft's path is also forcing free-software organizations to be unable to invent any hardware interop systems, VPN, file systems and more with these certificate enforcements since economically only the bigger companies will afford the certificates.
Reference articles:
Also here is an article about what's now impossible to do without legitimate certificates in Windows 10 http://ift.tt/1Kgj8C7
Aucun commentaire:
Enregistrer un commentaire