Restructure of mono.sln and build properties to better fix static/dynamic library...

[mono.git] / man / signcode.1

diff --git a/man/signcode.1 b/man/signcode.1
old mode 100755 (executable)
new mode 100644 (file)
index 3a65fd4..7771826
--- a/man/signcode.1
+++ b/man/signcode.1
@@ -1,8 +1,9 @@
 .\" 
 .\" signcode manual page.
 .\" Copyright 2003 Motus Technologies
+.\" Copyright 2004 Novell
 .\" Author:
-.\"   Sebastien Pouliot (spouliot@motus.com)
+.\"   Sebastien Pouliot (sebastien@ximian.com)
 .\"
 .TH Mono "signcode"
 .SH NAME
@@ -13,7 +14,8 @@ signcode \- Digitally sign an PE executable using an X.509 certificate.
 .SH DESCRIPTION
 Digitally sign an PE executable (CLR assembly, Win32 EXE or DLL) using an 
 X.509 certificate and it's associated private key. The signature is compatible
-with Authenticode(r) and can be validated with chktrust.
+with Authenticode(r) and can be validated with chktrust (either on Windows or
+on any platform supported by Mono).
 .SH OPTIONS
 .TP
 .I "-spc spcfile"
@@ -25,9 +27,9 @@ The Private Key File (pvk) that contains the private key used to digitally
 sign the PE executable. This private key must match the public key inside the
 publisher X.509 certificate.
 .TP
-.I "-a md5 | sha1"
+.I "-a sha1 | md5"
 The hash algorithm used in the digital signature of the PE executable. The 
-default algorithm is MD5.
+default algorithm is SHA1.
 .TP
 .I "-$ individual | commercial"
 Add information about the publisher, i.e. if the signature is generated by an
@@ -48,7 +50,7 @@ had a valid (non-expired) certificate when the PE executable was signed.
 .I "-tr #"
 Number of retries to get a timestamp for the countersignature.
 .TP
-.I "-td #"
+.I "-tw #"
 Delay (in seconds) between the retries to get a timestamp for the countersignature.
 .TP
 .I "-k name"
@@ -68,14 +70,24 @@ CryptoAPI key location (when not using -v).
 .TP
 .I "-help", "-h", "-?", "/?"
 Display help about this tool.
+.SH OTHER CODE SIGNING TECHNOLOGIES
+Assemblies are PE files that can also be strongnamed using the sn.exe tool. The 
+order of code signature is important if a file requires both an Authenticode 
+and a strongname signature. Strongname must be applied before the Authenticode 
+signature. Applying a strongname after the Authenticode signature, like 
+re-signing an assembly (e.g. delay-sign), will invalidate the Authenticode 
+signature.
+.SH KNOWN RESTRICTIONS
+signcode cannot generate Authenticode signatures for CAB files.
 .SH AUTHOR
 Written by Sebastien Pouliot
 .SH COPYRIGHT
 Copyright (C) 2003 Motus Technologies. 
+Copyright (C) 2004 Novell.
 Released under BSD license.
 .SH MAILING LISTS
-Visit http://mail.ximian.com/mailman/mono-list for details.
+Visit http://lists.ximian.com/mailman/listinfo/mono-devel-list for details.
 .SH WEB SITE
-Visit: http://www.go-mono.com for details
+Visit http://www.mono-project.com for details
 .SH SEE ALSO
 .BR chktrust(1), makecert(1), cert2spc(1)