tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

index.rst (4479B)

      1 .. _mozilla_projects_nss_reference_nss_tools_:_cmsutil:
      2 
      3 NSS tools : cmsutil
      4 ===================
      5 
      6 .. container::
      7 
      8   Name
      9 
     10   | cmsutil — Performs basic cryptograpic operations, such as encryption and
     11   | decryption, on Cryptographic Message Syntax (CMS) messages.
     12 
     13   Synopsis
     14 
     15   cmsutil [options] `arguments <arguments>`__
     16 
     17   Description
     18 
     19   | The cmsutil command-line uses the S/MIME Toolkit to perform basic
     20   | operations, such as encryption and decryption, on Cryptographic Message
     21   | Syntax (CMS) messages.
     22 
     23   | To run cmsutil, type the command cmsutil option [arguments] where option
     24   | and arguments are combinations of the options and arguments listed in the
     25   | following section. Each command takes one option. Each option may take
     26   | zero or more arguments. To see a usage string, issue the command without
     27   | options.
     28 
     29   Options and Arguments
     30 
     31   Options
     32 
     33   | Options specify an action. Option arguments modify an action. The options
     34   | and arguments for the cmsutil command are defined as follows:
     35 
     36   -D
     37 
     38   Decode a message.
     39 
     40   -C
     41 
     42   Encrypt a message.
     43 
     44   -E
     45 
     46   Envelope a message.
     47 
     48   -O
     49 
     50   Create a certificates-only message.
     51 
     52   -S
     53 
     54   Sign a message.
     55 
     56   Arguments
     57 
     58   Option arguments modify an action and are lowercase.
     59 
     60   -c content
     61 
     62   Use this detached content (decode only).
     63 
     64   -d dbdir
     65 
     66   Specify the key/certificate database directory (default is ".")
     67 
     68   -e envfile
     69 
     70   | Specify a file containing an enveloped message for a set of
     71   | recipients to which you would like to send an encrypted message.
     72   | If this is the first encrypted message for that set of recipients,
     73   | a new enveloped message will be created that you can then use for
     74   | future messages (encrypt only).
     75 
     76   -G
     77 
     78   Include a signing time attribute (sign only).
     79 
     80   -h num
     81 
     82   Generate email headers with info about CMS message (decode only).
     83 
     84   -i infile
     85 
     86   Use infile as a source of data (default is stdin).
     87 
     88   -N nickname
     89 
     90   Specify nickname of certificate to sign with (sign only).
     91 
     92   -n
     93 
     94   Suppress output of contents (decode only).
     95 
     96   -o outfile
     97 
     98   Use outfile as a destination of data (default is stdout).
     99 
    100   -P
    101 
    102   Include an S/MIME capabilities attribute.
    103 
    104   -p password
    105 
    106   Use password as key database password.
    107 
    108   -r recipient1,recipient2, ...
    109 
    110   | Specify list of recipients (email addresses) for an encrypted or
    111   | enveloped message. For certificates-only message, list of
    112   | certificates to send.
    113 
    114   -T
    115 
    116   Suppress content in CMS message (sign only).
    117 
    118   -u certusage
    119 
    120   Set type of cert usage (default is certUsageEmailSigner).
    121 
    122   -Y ekprefnick
    123 
    124   Specify an encryption key preference by nickname.
    125 
    126   Usage
    127 
    128   Encrypt Example
    129 
    130   cmsutil -C [-i infile] [-o outfile] [-d dbdir] [-p password] -r "recipient1,recipient2, . . ." -e
    131   envfile
    132 
    133   |
    134   | Decode Example
    135 
    136   cmsutil -D [-i infile] [-o outfile] [-d dbdir] [-p password] [-c content] [-n] [-h num]
    137 
    138   |
    139   | Envelope Example
    140 
    141   cmsutil -E [-i infile] [-o outfile] [-d dbdir] [-p password] -r "recipient1,recipient2, ..."
    142 
    143   |
    144   | Certificate-only Example
    145 
    146   cmsutil -O [-i infile] [-o outfile] [-d dbdir] [-p password] -r "cert1,cert2, . . ."
    147 
    148   |
    149   | Sign Message Example
    150 
    151   cmsutil -S [-i infile] [-o outfile] [-d dbdir] [-p password] -N nickname[-TGP] [-Y ekprefnick]
    152 
    153   |
    154   | See also
    155 
    156   certutil(1)
    157 
    158   See Also
    159 
    160   Additional Resources
    161 
    162   | NSS is maintained in conjunction with PKI and security-related projects
    163   | through Mozilla dn Fedora. The most closely-related project is Dogtag PKI,
    164   | with a project wiki at [1]\ http://pki.fedoraproject.org/wiki/.
    165 
    166   | For information specifically about NSS, the NSS project wiki is located at
    167   | [2]\ `http://www.mozilla.org/projects/security/pki/nss/ <https://www.mozilla.org/projects/security/pki/nss/>`__.
    168     The NSS site relates
    169   | directly to NSS code changes and releases.
    170 
    171   Mailing lists: pki-devel@redhat.com and pki-users@redhat.com
    172 
    173   IRC: Freenode at #dogtag-pki
    174 
    175   Authors
    176 
    177   | The NSS tools were written and maintained by developers with Netscape and
    178   | now with Red Hat.
    179 
    180   | Authors: Elio Maldonado <emaldona@redhat.com>, Deon Lackey
    181   | <dlackey@redhat.com>.
    182 
    183   Copyright
    184 
    185   (c) 2010, Red Hat, Inc. Licensed under the GNU Public License version 2.
    186 
    187   References
    188 
    189   | Visible links
    190   | 1. http://pki.fedoraproject.org/wiki/
    191   | 2.
    192     `http://www.mozilla.org/projects/security/pki/nss/ <https://www.mozilla.org/projects/security/pki/nss/>`__