SmimeIncludeWholeChainOnSign Property |
Namespace: MailBee.Security
With the whole chain, the signature size will be larger. However, if you set this value to false, it might not be possible for the recipient to check the signature in case if the CA of this certificate is not known for them.
Note |
---|
If you're getting "System.Security.Cryptography.CryptographicException: the buffer supplied to a function was too small" on signing, you will have to set this property to false. Some combinations of Windows (Windows Server 2012) and .NET Framework have a bug in an underlying implementation of security certificates which cannot be worked around unless you upgrade to a more recent Windows (e.g. 2016) or disable including the whole certificate chain. Issue on github.com. |