3
votes
Vote UpVote

Code Signing Changes for 2016

VSoft Technologies – Microsoft announced some time ago that windows 7 & higher would no longer trust anything that is code signed with an SHA1 (https://en.wikipedia.org/wiki/SHA-1 ) certificate as of 1st Jan 2016. The reason for this is well documented, SHA1 has become increasingly vulnerable and is no longer secure enough to be trusted. What do I need to do? First things first, check your code signing certificate. If it's current, and uses SHA1, contact your certificate issuer for a replacement SHA256 certificate. Most issuers have a formal process for this since this is something they have known about for ...
Favorite? Off-Topic? 2016-01-20 06:18

Statistics

Visits: 1500
Votes: 3
Favorites: 1
Off-Topic: 1

Visits by Source

User Actions

Users who voted for this posting

Alister Christie
GunSmoker
slr4bf
Subscribe:
Contact us to advertise on DelphiFeeds.com

Community Links

Torry Firebird News

Sponsor

 
Please login or register to use this functionality.
(click on this box to dismiss)