Support for SHA256 code signing

[tonyedgecombe]

As 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) 

[swanitzek]

I have the same problem.

Even appening the required argument via the ArgumentBuilder isn't possible because the order of the arguments passed to signtool matters.

A valid command line for signing a file with SHA256 looks like this:

signtool.exe SIGN /sha1 "<THUMBPRINT>" /fd sha256 "File.exe"

A possible workaround is to prepare the correct argument string manually and call signtool.exe directly.

[patriksvensson]

@swanitzek You can slso return a new ProcessArgumentBuilder from the ArgumentCustomization lambda and rewrite all parameters that way.

[bjorkstromm]

@patriksvensson, mind if I take a stab on this one? Needed to sign using sha256 today, and doing the ArgumentCustomization dance was a ugly workaround.

[devlead]

@mholo65 Perfect I've assigned this issue to you.

[gep13]

Big thanks to @mholo65 for implementing this!