4 ms·
Wow - while looking at the changelog, I found that there's a working btrfs driver for Windows/ReactOS. https://github.com/maharmstone/btrfs https://github.com/
by voltagex_ 10y ago
Wow - while looking at the changelog, I found that there's a working btrfs driver for Windows/ReactOS.
https://github.com/maharmstone/btrfs https://github.com/maharmstone/btrfs
Of course, Microsoft's driver signing changes make it a very expensive proposition to run on Windows 10, unfortunately.
- shawnz 10y agoYou could sign it yourself and install that certificate into your system. A certificate that will work for everyone would cost about $200/year, which I don't think is too unreasonable.
- NegativeLatency 10y agoIf the software is open source Microsoft should be good enough to have a pathway for people to get it out for free.
- colordrops 10y agoMicrosoft still has some vestigial stupidity from their past culture. It would only help them if they opened up for open source projects like this.
- wila 10y agoThere's relatively cheap code signing [0] certificates specifically for open source. There might be completely free alternatives too, not sure about that, but EUR 28 is not a lot. [0] https://www.certum.eu/certum/cert,offer_en_open_source_cs.xml https://www.certum.eu/certum/cert,offer_en_open_source_cs.xm... [1] http://stackoverflow.com/questions/1177552/code-signing-certificate-for-open-source-projects http://stackoverflow.com/questions/1177552/code-signing-cert...
- poizan42 10y agoI think you need an EV certificate from one of 5 providers to sign drivers that works on Windows 10 now.
- wila 10y agoYes, you are correct. This has been enforced now since build 1607. So no way to get a driver signed cheaply anymore. [0] https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/ https://blogs.msdn.microsoft.com/windows_hardware_certificat...
- poizan42 10y agoI think there is something about "getting the driver signed from the dashboard", seems like Microsoft will sign it if it passes WHQL certification. But it is really hard to find any coherent information about how it all works. Seems that everything is kept obscure if you are not a big hardware company. Something as simple as getting a list of which certificates that will work seems practically impossible. The only useful information seems to be from blog posts and forum discussions at osronline. Of course malware authors don't care much about all this since they just find some old version of a driver with a known vulnerability, so the only it accomplishes is keeping a high barrier to entry.
- voltagex_ 10y agoI don't even think signing it with a trusted root certificate will work in this case.