My company runs the Microsoft Security Code Analysis toolset to audit our managed and unmanaged code. BinSkim is one of those tools and reports the following issue with the Dapper.Oracle Nuget package:
BinSkim error BA2022: Images should be correctly signed by trusted publishers using cryptographically secure signature algorithms.
Error details:
Images should be correctly signed by trusted publishers using cryptographically secure signature algorithms. This rule invokes WinTrustVerify to validate that binary hash, signing and public key algorithms are secure and, where configurable, that key sizes meet acceptable size thresholds.
My company runs the Microsoft Security Code Analysis toolset to audit our managed and unmanaged code. BinSkim is one of those tools and reports the following issue with the Dapper.Oracle Nuget package:
BinSkim error BA2022: Images should be correctly signed by trusted publishers using cryptographically secure signature algorithms.
Error details:
Images should be correctly signed by trusted publishers using cryptographically secure signature algorithms. This rule invokes WinTrustVerify to validate that binary hash, signing and public key algorithms are secure and, where configurable, that key sizes meet acceptable size thresholds.
Cryptographically weak signatures: [digest algorithm: 'sha1NoSign' + digest encryption algorithm: 'RSA']
Could you please sign your package using SHA-2 signatures?