エラーとソリューション
ヒント
When you sign a manifest file using mage, two signature units are consumed. This is because two hash signatures are created for different types of content within the manifest:
The first hash signature is generated for the manifest file itself.
The second hash signature is generated for the files referenced within the manifest.
This double-signing process ensures the integrity of both the manifest file and its referenced files, safeguarding against any tampering attempts.
Internal error, invalid provider type specified when using certificate hash to sign
Error message
Internal error, please try again. Invalid provider type specified.
Problem
This is a general error and can occur due to many reasons.
Solution
Check environment variables required for DigiCert® Software Trust Manager are configured properly. If that does not solve the issue, then check the DigiCert® Software Trust Manager KSP log file at .signingmanager\logs\smksp.log. This will provide you with more details on why the operation failed. The Home directory on Windows is usually at C:\Users\<User Name>
This certificate does not contain a private key when using a certificate file to sign
Error message
This certificate does not contain a private key - "C:\Workspace\smtools-windows\RSA-2048-Test.crt", if this is a public key certificate, please provide valid cryptographic service provider and key container names
Problem
This is a general error and can occur due to many reasons.
Solution
Check environment variables required for DigiCert® Software Trust Manager are configured properly. If that does not solve the issue, then check the DigiCert® Software Trust Manager KSP log file at .signingmanager\logs\smksp.log. This will provide you with more detail on why the operation failed. The Home directory on Windows is usually at C:\Users\<User Name>