Support for SHA256 code signing
See original GitHub issueAs of 1st January Microsoft no longer accepts SHA1 certificates for code signing.
The existing Sign code does not support SHA256 signing and timestamps.
The required options are:
/fd File digest algorithm
/tr RFC 3161 compatible time stamp server
/td Timestamp digest algorithm
/as Append signature (to enable signing for XP and Vista)
Issue Analytics
- State:
- Created 8 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
2019 SHA-2 Code Signing Support requirement for ...
The signatures are used to authenticate that the updates come directly from Microsoft and were not tampered with during delivery. Because of weaknesses...
Read more >The truth about SHA1, SHA-256, dual-signing and Code ...
The truth about SHA1, SHA-256, dual-signing and Code Signing Certificates ... SHA-256 signatures are not supported in Windows XP SP2 or earlier.
Read more >Dual Sign a File with SHA-256 & SHA1 Code ...
Learn all the commands to dual sign and include SHA-1 signature file on platforms that don't support SHA256 Timestamps or File Digests.
Read more >SHA1, SHA-256, dual-signing, and Code Signing - What It is?
Any new signatures created or timestamped after Jan 1, 2016, must be SHA-256 based signatures or they will cause a "digital signature is...
Read more >Windows Code Signing Hash Algorithm Support
Although your Code Signing Certificate may be signed by GlobalSign to verify its integrity, when you sign code, you may also specify the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@swanitzek You can slso return a new ProcessArgumentBuilder from the ArgumentCustomization lambda and rewrite all parameters that way.
Big thanks to @mholo65 for implementing this!