[Mono-bugs] [Bug 51057][Nor] Changed - Test MonoTests.System.Security.Cryptography.X509Certificates.ValidSignature fails
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Mon, 15 Dec 2003 12:39:51 -0500 (EST)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by spouliot@videotron.ca.
http://bugzilla.ximian.com/show_bug.cgi?id=51057
--- shadow/51057 2003-11-17 00:23:56.000000000 -0500
+++ shadow/51057.tmp.26354 2003-12-15 12:39:51.000000000 -0500
@@ -1,14 +1,14 @@
Bug#: 51057
Product: Mono/Class Libraries
Version: unspecified
-OS:
+OS: unknown
OS Details: Windows .NET 1.1
-Status: NEW
+Status: ASSIGNED
Resolution:
-Severity:
+Severity: Unknown
Priority: Normal
Component: CORLIB
AssignedTo: mono-bugs@ximian.com
ReportedBy: ndrochak@gol.com
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
@@ -32,6 +32,19 @@
gnedFile(String filename)
at
MonoTests.System.Security.Cryptography.X509Certificates.X509SPCTest.ValidS
ignature() in
c:\cygwin\home\nickdr\mcs\class\corlib\Test\System.Security.Crypto
graphy.X509Certificates\X509SpcTest.cs:line 870
+
+------- Additional Comments From spouliot@videotron.ca 2003-12-15 12:39 -------
+This is (most probably) because the signatures were done using a
+test certificate - which (by default - and with VERY good reasons)
+isn't trusted on Windows.
+
+I changed the unit test to use an assembly signed by a "real" code
+signing certificate - so now it should work under Windows (without
+messing into the configuration).
+
+I also discovered some bugs in Authenticode and added a new trusted
+root (Thawte) so you'll have to sync mscorlib with CVS before
+testing.