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 37535 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
Created attachment 14507 [details]
A minimal program that demonstrates the signing and verification bug.
When an xml file containing a newline within a non-empty (meaning whitespace only) tag content is encrypted and signed using a program running under the .Net runtime, that file cannot be verified by the same program running under the mono runtime (and visa versa).
If the xml file does not contain a newline within a non-empty tag content, this error does not exist.
In other words...
This verifies fine: <a>.</a>
This fails verification under mono: <a>.\n</a>
A minimal demonstration program is attached.
After extensive testing I have isolated the issue to mono's implementation of the SignedXml class. To wit, if I copy mono's SignedXml class into my project as MySignedXml, and replace all references to SignedXml with MySignedXml, then the program behaves under .Net the same as it behaves under Mono.