[Mono-bugs] [Bug 690057] New: GetXmlDigitalSignature with RSACryptoServiceProvider: different signature under Win and Linux

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=690057

https://bugzilla.novell.com/show_bug.cgi?id=690057#c0


           Summary: GetXmlDigitalSignature with RSACryptoServiceProvider:
                    different signature under Win and Linux
    Classification: Mono
           Product: Mono: Runtime
           Version: unspecified
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: interop
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: rene at pilz.cc
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.16)
Gecko/20110322 Fedora/3.6.16-1.fc14 Firefox/3.6.16

When creating a signed XML with GetXmlDigitalSignature (using
RSACryptoServiceProvider) the MONO-Runtime generates different signatures than
the Windows-Version of .NET.

I've included a MonoDevelop-Project to verify this issue. I've done testings
under different .NET-Runtimes (and therefore different Windows-Machines) and
different mono-Versions under different Linux-Distributions (mostly Ubuntu and
Fedora).

Mono allways creates the same Signatue "MONOSIG"
and Windows allways creates "DOTNETSIG" 
but "MONOSIG" is not the same that "DOTNETSIG"

Reproducible: Always

Steps to Reproduce:
1. eather use the monodevelop-project within the zip-file or 
2. just extract cryptoTest.exe and privateKey.xml into the same folder and run
cryptoTest.exe (eather mono cryptoTest.exe or under Windows just start
cryptoTest.exe)
3.
Actual Results:  
Windows and Mono-Signatures are different

Expected Results:  
Windows and Mono-Signatures should be the same

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.