dokanx
dokanx copied to clipboard
BenjaminKim
Driver signing
Eventually signed drivers are going to be needed:
Here's a potential workaround for a while: https://github.com/koush/UniversalAdbDriver/blob/master/UniveralAdbDriverInstaller/Program.cs
Basically, create a certificate that's distributed with an installer. Before the driver is installed, the certificate is added to the root store.
ReactOS sign opensource drivers for free.
You should contact them: https://www.reactos.org/wiki/Driver_Signing
@Shamar I didn't know about that. Thank you for informing this. I will try that.
Please, let us know about any progress about this matter. Driver signature is the only issue that is preventing our team to adopt dokanx for a few internal tools.
My employers are evaluating DokanX as a possible platform to help create a Windows mountable Virtual File System (Fuse and OSXFuse has served us well for Linux and Mac OS X). Distribution will be an issue unless the Kernel Driver is signed. Please keep us updated on any progress on this front.
https://github.com/Maxhy/dokany have a signed version of Dokan synced with DokanX.
@jimmy00784 are you planning to use/join/start an open source project? I'm designing exactly the same thing.
@Shamar Not exactly. It is for use within a non-open source commercial project. There are other open source projects we are utilizing without altering their sources as library dependencies and including the necessary Licenses to go with them.
I have sent an email to ReactOS foundation. I am not sure they accept this yet. I will keep informing that.
El Friday 27 March 2015, Karim Lalani escribió:
@BenjaminKim We are only weeks from launching our product to market and a signed driver is essential to providing virtual FS support under Windows. Our only other option would be to rewrite our own FS driver outside of DokanX.
My employers have offered to assist with getting the DokanX driver signed. Let me know if you are interested pursue this path at your earliest.
Have you given a try to DokanY's driver? The project, driver wise, seems aligned completely. The difference is in the library: DokanX has support for std::function instead of a plain C callback. If you can resort to the latter, or use a wrapper, I think you can achieve at least source and behaviour compatibility.
I can sign drivers thru the Outercurve Foundation.
Let me spin up my Win7 development VM and see if I can build this. If I get the build running right, it's trivial for me to sign it.
G
Good to see you here, Garrett. Is the signing something that could be put into a CI system? On 7 Apr 2015 9:21 am, "Garrett Serack" [email protected] wrote:
I can sign drivers thru the Outercurve Foundation.
Let me spin up my Win7 development VM and see if I can build this. If I get the build running right, it's trivial for me to sign it.
G
— Reply to this email directly or view it on GitHub https://github.com/BenjaminKim/dokanx/issues/15#issuecomment-90281886.
@voltagex Um, I could probably put a CI system in place for it, I should do that for OneGet anyway.
Any updates on this @fearthecowboy? (and a couple of other things I asked you a while back...)
@voltagex You should look at DokanY (https://github.com/dokan-dev/dokany) The project is probably the most serious fork of dokan and kindly signed by a company. It also looks like the maintainers are using Dokan their self, so it give a good vision of the stability and evolution of the DokanY fork. You can also see that they have contact all project arround Dokan to recreate the community.
I was a DokanX user and I moved to DokanY in a minute since there is no big change.
I will sign the driver and make a pull request next week. So you will have signed drivers for every release
