.\"
.\" 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
.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"
.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"
.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)