tor-browser

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

index.rst (4957B)


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