Seth Woolley's Man Viewer

sn(1) - sn - Digitally sign/verify/compare strongname on CLR assemblies - man 1 sn

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

Mono(sn)                                                              Mono(sn)



NAME
       sn - Digitally sign/verify(1,8)/compare strongname on CLR assemblies.

SYNOPSIS
       sn [-q | -quiet] [options] [parameters]

DESCRIPTION
       Digitally sign, verify(1,8) or compare, CLR assemblies using strongnames.

CONFIGURATION OPTIONS
       Configuration  options  are  stored in(1,8) the machine.config configuration
       file(1,n) under /configuration/strongNames.

       -c provider
              Change the default CSP (Crypto Service Provider). Currently  not
              supported in(1,8) Mono.

       -m [y|n]
              Use  a  machine  [y]  key container or a user [n] key container.
              Currently not supported in(1,8) Mono.

       -Vl    List the verification options. The list is kept under  /configu-
              ration/ strongNames/verificationSettings in(1,8) machine.config.

       -Vr assembly [userlist]
              Exempt  the  specified assembly from verification for the speci-
              fied user list.  Currently not supported by sn,  you  must  edit
              machine.config manually if(3,n) you require this.

       -Vu assembly
              Remove the exemption entry for the specified assembly. Currently
              not supported by sn, you must edit  machine.config  manually  if(3,n)
              you require this.

       -Vx    Remove  all  exemptions  entries. Currently not supported by sn,
              you must edit machine.config manually if(3,n) you require this.

CSP RELATED OPTIONS
       -d container
              Delete the keypair present in(1,8) the specified key container.

       -i keypair.snk container
              Import the specified strongname file(1,n)  into  the  specified  con-
              tainer.

       -pc container publickey
              Export  the  public  key from the specified CSP container to the
              specified file.

CONVERTION OPTIONS
       -e assembly output.pub
              Export the assembly public key to the specified output file.

       -p keypair.snk output.pub
              Export the public key from the  specified  strongname  key  file(1,n)
              (SNK) to the specified output file.

       -o input output.txt
              Convert the input file(1,n) to a CSV file(1,n) (using decimal).

       -oh input output.txt
              Convert the input file(1,n) to a CSV file(1,n) (using hexadecimal).

STRONGNAME SIGNING OPTIONS
       -D assembly1 assembly2
              Compare  if(3,n)  assembly1  and  assembly are the same exception for
              their signature.  This is done by  comparing  the  hash  of  the
              metadata of both assembly.

       -k keypair.snk
              Create a new strongname keypair (a 1024 bits RSA keypair) in(1,8) the
              specified file.

       -R assembly keypair.snk
              Resign the specified assembly  using  the  specified  strongname
              keypair  file(1,n) (SNK). You can only sign an assembly with the pri-
              vate key (SNK) that match the public  key  inside  the  assembly
              (unless  it's public key token has been remapped in(1,8) machine.con-
              fig).

       -Rc assembly container
              Resign the specified assembly  using  the  specified  strongname
              container.

       -t file(1,n)
              Show the public key from the specified file.

       -tp file(1,n)
              Show  the public key and the public key token from the specified
              file.

       -T assembly
              Show the public key from the specified assembly.

       -Tp assembly
              Show the public key and the public key token from the  specified
              assembly.

       -v assembly
              Verify the specified assembly signature.

       -vf assembly
              Verify the specified assembly signature (even if(3,n) disabled).

HELP OPTIONS
       -h , -?
              Display basic help about this tool.

       -h config(1,5) , -? config(1,5)
              Display configuration related help about this tool.

       -h csp , -? csp
              Display  Cryptographic  Service Provider related help about this
              tool.

       -h convert , -? convert
              Display convertion related help about this tool.

       -h sn , -? sn
              Display strongname related help about this tool.

CONFIGURATION FILE
       Strongnames configuration is kept in(1,8) "machine.config"  file.  Currently
       two
              features can be configured.

       /configuration/strongNames/pubTokenMapping
              This mechanism let Mono remap a public key token, like the  ECMA
              token, to another public key for verification. This is useful in(1,8)
              two scenarios. First assemblies signed with the "ECMA key" needs
              to  be  verified  by  the "runtime" key (as the ECMA key isn't a
              public key). Second, many assemblies  are  signed  with  private
              keys that Mono can't use (e.g. System.Security.dll assembly).  A
              new key cannot be used because it should change  thr  strongname
              (a  new key pair would have a new public key which would produce
              a new token). Public key token remapping  is  the  solution  for
              both  problems.  Each  token must be configured in(1,8) a "map" entry
              similar  to  this  one:   <map   Token="b77a5c561934e089"   Pub-
              licKey="00..." />

       /configuration/strongNames/verificationSettings
              It is often useful during development to use delay signed assem-
              blies.  Normally* the runtime wouldn't allow delay-signed assem-
              blies  to  be  loaded.   This  feature  allows some delay-signed
              assemblies (based on their public key token, optionally assembly
              name  and  user  name)  to  be  used like they were fully signed
              assemblies. [*] Note that Mono 1.0  "runtime"  doesn't  validate
              strongname  signatures  so  this option shouldn't be required in(1,8)
              most scenarios.

AUTHOR
       Written by Sebastien Pouliot

COPYRIGHT
       Copyright (C) 2003 Motus  Technologies.   Copyright  (C)  2004  Novell.
       Released under BSD license.

MAILING LISTS
       Visit http://lists.ximian.com/mailman/listinfo/mono-list for details.

WEB SITE
       Visit http://www.mono-project.com for details

SEE ALSO
       secutil(1)



                                                                      Mono(sn)

References for this manual (incoming links)