Dokan 1.0.0 on Windows 10

Kyle Hamilton

unread,

Sep 8, 2016, 4:36:23 AM9/8/16

to do...@googlegroups.com

On July 26, Microsoft announced new kernel driver signing requirements
for Windows 10 build 1607.
https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/

What plans exist, if any, to ensure that DokanY can/will be properly
signed by Microsoft for use on Secure Boot enabled computers running
fresh installations of Windows 10? Note that these new requirements
mandate the obtainment and use of an Extended Validation code-signing
certificate to submit kernel-mode drivers to be signed. Is there a
foundation for DokanY development that can obtain an EV code-signing
certificate to comply with these new requirements?

Thanks!

-Kyle H

Adrien JUND

unread,

Sep 8, 2016, 4:38:39 AM9/8/16

to do...@googlegroups.com

Hi Kyle,

This is already done :)

See https://github.com/dokan-dev/dokany/issues/271

Best regards

--
You received this message because you are subscribed to the Google Groups "Dokan" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dokan+unsubscribe@googlegroups.com.
To post to this group, send email to do...@googlegroups.com.
Visit this group at https://groups.google.com/group/dokan.
For more options, visit https://groups.google.com/d/optout.

Carl Appellof

unread,

Mar 28, 2017, 5:12:06 PM3/28/17

to Dokan

Are there any plans to get a MIcrosoft signature for newer releases of the driver, such as version 1.0.3 that was just released?

Thanks,
Carl

On Thursday, September 8, 2016 at 1:38:39 AM UTC-7, Liryna wrote:

Hi Kyle,

This is already done :)
See https://github.com/dokan-dev/dokany/issues/271

Best regards

On Thu, Sep 8, 2016 at 10:36 AM, Kyle Hamilton <kya...@kyanha.net> wrote:

On July 26, Microsoft announced new kernel driver signing requirements
for Windows 10 build 1607.
https://blogs.msdn.microsoft.com/windows_hardware_certification/2016/07/26/driver-signing-changes-in-windows-10-version-1607/

What plans exist, if any, to ensure that DokanY can/will be properly
signed by Microsoft for use on Secure Boot enabled computers running
fresh installations of Windows 10? Note that these new requirements
mandate the obtainment and use of an Extended Validation code-signing
certificate to submit kernel-mode drivers to be signed. Is there a
foundation for DokanY development that can obtain an EV code-signing
certificate to comply with these new requirements?

Thanks!

-Kyle H

--
You received this message because you are subscribed to the Google Groups "Dokan" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dokan+un...@googlegroups.com.

Liryna

unread,

Mar 29, 2017, 1:36:54 AM3/29/17

to Dokan

Hi Carl,

We already have Microsoft signature since release 1.0.0
You can use dokan with secure boot and windows server 2016 without issues.

Best regards,

Carl Appellof

unread,

Apr 3, 2017, 12:54:34 PM4/3/17

to Dokan

Thanks for the clarification. I had installed 1.0.3 on my Windows 2012R2 system and did not see a Microsoft signature on the driver (no need for one on that platform.) Then I installed on my Windows 2016 Server system with secure boot. Driver has a MS signature there, and is running fine. I'm used to producing a single driver that runs on all systems, so I made an assumption that dokan1.sys was the same. Glad to see there's a good signed version for newer Windows platforms.