Troubleshooting Most Common Mage Errors while Sign a Manifest File

Mage Errors and Solutions

Introduction

When signing a manifest file using mage, two signature units are used. This is because two separate hash signatures are created for different aspects of the manifest.

  • Manifest File Hash Signature: The first hash signature is generated for the manifest file, which ensures the integrity and authenticity of the manifest.
  • Referenced Files Hash Signature: The second hash signature is created for the files referenced within the manifest to protect the integrity of the files listed in the manifest.

This dual-signing process safeguards both manifest and referenced files against any unauthorized modifications.

Common Mage Errors

Internal error, invalid provider type specified when using certificate hash to sign

Error Message

Internal error, please try again. Invalid provider type specified.

Why does this Error occur?

This is a general error that occurs due to various reasons.

Solution

Check Environment Variables

  • Verify paths and credentials are accurate and accessible.

Review Log Files

  • If the issue persists, check the DigiCert Software Trust Manager KSP log file for detailed information about the failure.
  • The log file is located at .signingmanager\logs\smksp.log.
  • On Windows, the home directory is typically found at C:\Users\<User Name>.

Internal Error, Invalid provider type specified when using certificate hash 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

Why does this error occur?

 This is a general error that occurs due to various reasons.

Solution

  • Ensure all environment variables required for DigiCert® Software Trust Manager are correctly configured. Verify if the paths, credentials, and configurations are accurate and accessible.
  • If the problem persists, examine the DigiCert® Software Trust Manager KSP log file for more detailed information on the error. The log file is located at .signingmanager\logs\smksp.log. On Windows, the home directory is typically found at C:\Users\<User Name>.

Conclusion

Hope you have successfully fixed the mage issue by following the above steps.

Code Signing Tutorials

Cheap Code Signing Certificates

Prevent Code Tampering and Authenticate Code Integrity by Digitally Sign your Code with Trusted Code Signing Certificates.

Starting at Just $215.99/Year
Janki Mehta

Janki Mehta

Janki Mehta is a Cyber-Security Enthusiast who constantly updates herself with new advancements in the Web/Cyber Security niche. Along with theoretical knowledge, she also implements her practical expertise in day-to-day tasks and helps others to protect themselves from threats.