Re: Summary of Digital Certificate and Windows 10

Hi.
I think this came to me by mistake. I'm not involved in this thread. Thanks.

Regards,
Derek Best
Dazzle Systems Inc.
(888) 88-DAZZLE
(248) 687-6666
UK No. (0845) 862-0763
www.dazzlepawn.com

-----Original Message-----
From: Travis [mailto:[email protected]] 
Sent: Tuesday, August 18, 2015 10:26 AM
To: [email protected]
Subject: Re: [Libusb-win32-devel] Summary of Digital Certificate and Windows
10

Greetings,

Everything we sign is timestamped.  This means anything we sign before
21-June-2017 remains valid after the certificate expires. IE.  Your installs
will not suddenly stop working on June-2017!

The June 2017 deadline simply means it's time to buy a new certificate if we
want to continue to make changes to libusbK.sys and release NEW updates.

Regards,
Travis

On 8/14/2015 7:55 AM, Xiaofan Chen wrote:
> So from the following summary, the DigiCert that Travis is using now 
> will still be good until it expires in  21-June-2017.
>
> Ref:
> https://www.osronline.com/showthread.cfm?link=268241
> Post 131.
>
> Confirmation:
> https://www.osronline.com/showthread.cfm?link=269119
>
>
>
> Regards,
> Xiaofan
>
>
> ___________
>
>
> On Thu, Aug 13, 2015 at 5:26 AM,  <[email protected]> wrote:
> Let me try to restate the rules (this is what we're planning to 
> publish in The NT Insider... so if it's wrong, I'd appreciate folks 
> letting me know):
>
> 1)       A driver signed with the standard SHA-1 certificate issued
> prior to the 29th of July and correctly cross-signed according to the 
> pre-Windows 10 KMCS procedures, will work on all platforms Vista 
> through to 10.  This is, however, subject to configurable an 
> enterprise-defined code integrity policy that is part of Device Guard 
> (available on Windows 10 Enterprise edition only).  This 
> enterprise-defined policy may be configured to require at least an 
> attestation-signed driver.
>
> 2)       A driver signed with an EV certificate issued prior to the
> 29th of July, and cross-signed according to the pre-Windows 10 KMCS 
> procedure, will work on 8 and above, and will work on Windows 7 / 
> Server 2008R2 if the patch issued through Windows Update earlier this 
> year has been applied. It won't work on Vista / Server 2008 though.
>
> 3)       A driver signed with any certificate issued after the 29th of
> July won't work on Windows 10, unless the driver is signed with a 
> Microsoft signature available through the SysDev portal.
>
> 4)       A portal-signed driver using attestation signing (which
> requires an EV certificate) will only work on Windows 10, unless also 
> signed with an additional valid certificate and cross-signed according 
> to the pre-Windows 10 KMCS procedure.
>
> 5)       A portal-signed driver that passes WLK tests (which requires
> an EV certificate) will work on Windows 7 through Windows 10.
>
> 6)       Windows Server vNext will only load portal-signed drivers
> that have successfully passed the WLK tests.
>
>   Peter
>   OSR
>   @OSRDrivers
>
> ----------------------------------------------------------------------
> -------- _______________________________________________
> Libusb-win32-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>


----------------------------------------------------------------------------
--
_______________________________________________
Libusb-win32-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel


---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com


------------------------------------------------------------------------------