SecureBlackbox 16: Troubleshooting: when you try to sign the data using the certificate contained in Windows (with a non-exportable private key), only the MD5 hash algorithm works, even if you manually specify a SHA* algorithm.
Note: This article applies only to SecureBlackbox Legacy. For future development please consider using the latest version.
The Windows CryptoAPI doesn't support SHA algorithms for signing by default, so SecureBlackbox reverts to MD5 if the CryptoAPI must be used for signing (this is the case of non-exportable private keys).
We appreciate your feedback. If you have any questions, comments, or suggestions about this article please contact our support team at kb@nsoftware.com.