[Mono-bugs] [Bug 68934][Nor] New - signcode/chktrust problem with timestamps

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 29 Oct 2004 11:10:47 -0400 (EDT)

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 sebastien@ximian.com.


--- shadow/68934	2004-10-29 11:10:47.000000000 -0400
+++ shadow/68934.tmp.4685	2004-10-29 11:10:47.000000000 -0400
@@ -0,0 +1,53 @@
+Bug#: 68934
+Product: Mono: Class Libraries
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: Mono.Security
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: sebastien@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: signcode/chktrust problem with timestamps
+Description of Problem:
+Mono version of signcode timestamp cannot be verified by MS tools.
+However Mono version of chktrust can verify it.
+Steps to reproduce the problem:
+1. makecert -r -n CN=Mono -sv publisher.pvk publisher.cer 
+2. cert2spc publisher.cer publisher.spc
+3. signcode -v publisher.pvk -spc publisher.spc -t
+http://timestamp.verisign.com/scripts/timstamp.dll test.exe
+4. chktrust -v test.exe
+Actual Results:
+Mono CheckTrust
+Copyright 2002, 2003 Motus Technologies. Copyright 2004 Novell. BSD licensed.
+Verifying file default.exe for Authenticode(tm) signatures...
+INFO! default.exe was timestamped on 10/29/2004 10:27:59 AM
+ERROR! default.exe signature can't be traced back to a trusted root!
+Expected Results:
+Using property pages on Windows we get the message that the "hash value is
+not correct".
+How often does this happen? 
+Additional Information:
+This used to work (a long time ago). A change in a related class must have
+broken this.