Will kernel mode driver signed with SHA-1 work after 2017?


i have kernel mode driver signed sha-1 certificates. original microsoft sha-1 deprecation policy, stop working after jan 1 2017. 

however, there major revision on sep 26 2016 on article: http://social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-sha1-certificates.aspx that seems code signing certificates not affected sha-1 deprecation anymore?

is true our sha-1 signed driver continue work after 2017 , no expiring issue anymore?

thanks!!

according revised policy, tls/ssl certificates affected sha1 deprecation. of other types unaffected enforcement. closest have come addressing code signing statement in policy. appears tbd. generally, if sha1 driver signed , has timestamp prior 2017, should fine.

post-february 2017 plan

after february 2017, intend more warn consumers risk of downloading software signed using sha-1 certificate. our goal develop common, os-level experience applications can use warn users weak cryptography sha-1.


mark b. cooper, president , founder of pki solutions inc., former microsoft senior engineer , subject matter expert microsoft active directory certificate services (adcs). known “the pki guy” @ microsoft 10 years. co-founder of revocent (revocent.com) , certaccord product offers linux certificate enrollment microsoft ca. connect mark @ https://www.pkisolutions.com



Windows Server  >  Security



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607