Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 36297 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
while experimenting and not really under standing the correct call sequences,
I tried this:
SignedCms cms = new SignedCms();
without calling Decode() first. This code is silently accepted by Mono, but
throw an exception under MS dot net:
Unhandled Exception: System.InvalidOperationException: The CMS message is not signed.
at System.Security.Cryptography.Pkcs.SignedCms.CheckSignature(X509Certificate2Collection extraStore, Boolean verifySignatureOnly)
at System.Security.Cryptography.Pkcs.SignedCms.CheckSignature(Boolean verifySignatureOnly)
Mono should throw an exception too.
Bump, need to check whether this problem still exists.
Was there any related code change recently to require a revisit? AFAIC, the class libraries, especially the security related ones, have not been worked on for years. I am not holding my breath for an update.