mirror of
https://repo.dactyloidae.xyz/Dactyloidae/UXP.git
synced 2026-09-21 15:57:31 +09:00
Replace NSS with Pale Moon's
This commit is contained in:
wuggy
parent
ff1e5e48bf
commit
8c2e376f94
2870 changed files with 1762232 additions and 1374220 deletions
|
|
@ -2,12 +2,12 @@
|
|||
.\" Title: CERTUTIL
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 5 October 2017
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "CERTUTIL" "1" "5 October 2017" "nss-tools" "NSS Security Tools"
|
||||
.TH "CERTUTIL" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
@ -187,6 +187,11 @@ Arguments modify a command option and are usually lower case, numbers, or symbol
|
|||
Use ASCII format or allow the use of ASCII format for input or output\&. This formatting follows RFC 1113\&. For certificate requests, ASCII output defaults to standard output unless redirected\&.
|
||||
.RE
|
||||
.PP
|
||||
\-\-simple\-self\-signed
|
||||
.RS 4
|
||||
When printing the certificate chain, don\*(Aqt search for a chain if issuer name equals to subject name\&.
|
||||
.RE
|
||||
.PP
|
||||
\-b validity\-time
|
||||
.RS 4
|
||||
Specify a time at which a certificate is required to be valid\&. Use when checking certificate validity with the
|
||||
|
|
@ -247,7 +252,7 @@ requests the legacy database
|
|||
.RE
|
||||
.sp
|
||||
If no prefix is specified the default type is retrieved from NSS_DEFAULT_DB_TYPE\&. If NSS_DEFAULT_DB_TYPE is not set then
|
||||
\fBdbm:\fR
|
||||
\fBsql:\fR
|
||||
is the default\&.
|
||||
.RE
|
||||
.PP
|
||||
|
|
@ -574,6 +579,18 @@ The contexts are the following:
|
|||
\fBJ\fR
|
||||
(as an object signer)
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
\fBI\fR
|
||||
(as an IPSEC user)
|
||||
.RE
|
||||
.RE
|
||||
.PP
|
||||
\-v valid\-months
|
||||
|
|
@ -1046,6 +1063,83 @@ msTrustListSign
|
|||
critical
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
x509Any
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
ipsecIKE
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
ipsecIKEEnd
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
ipsecIKEIntermediate
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
ipsecEnd
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
ipsecTunnel
|
||||
.RE
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
\h'-04'\(bu\h'+03'\c
|
||||
.\}
|
||||
.el \{\
|
||||
.sp -1
|
||||
.IP \(bu 2.3
|
||||
.\}
|
||||
ipsecUser
|
||||
.RE
|
||||
.sp
|
||||
X\&.509 certificate extensions are described in RFC 5280\&.
|
||||
.RE
|
||||
.PP
|
||||
|
|
@ -1199,7 +1293,7 @@ These databases must be created before certificates or keys can be generated\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-N \-d [sql:]directory
|
||||
certutil \-N \-d directory
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1213,7 +1307,7 @@ A certificate request contains most or all of the information that is used to ge
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-R \-k key\-type\-or\-id [\-q pqgfile|curve\-name] \-g key\-size \-s subject [\-h tokenname] \-d [sql:]directory [\-p phone] [\-o output\-file] [\-a]
|
||||
$ certutil \-R \-k key\-type\-or\-id [\-q pqgfile|curve\-name] \-g key\-size \-s subject [\-h tokenname] \-d directory [\-p phone] [\-o output\-file] [\-a]
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1279,7 +1373,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-R \-k rsa \-g 1024 \-s "CN=John Smith,O=Example Corp,L=Mountain View,ST=California,C=US" \-d sql:$HOME/nssdb \-p 650\-555\-0123 \-a \-o cert\&.cer
|
||||
$ certutil \-R \-k rsa \-g 1024 \-s "CN=John Smith,O=Example Corp,L=Mountain View,ST=California,C=US" \-d $HOME/nssdb \-p 650\-555\-0123 \-a \-o cert\&.cer
|
||||
|
||||
Generating key\&. This may take a few moments\&.\&.\&.
|
||||
|
||||
|
|
@ -1300,7 +1394,7 @@ command option\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-S \-k rsa|dsa|ec \-n certname \-s subject [\-c issuer |\-x] \-t trustargs \-d [sql:]directory [\-m serial\-number] [\-v valid\-months] [\-w offset\-months] [\-p phone] [\-1] [\-2] [\-3] [\-4] [\-5 keyword] [\-6 keyword] [\-7 emailAddress] [\-8 dns\-names] [\-\-extAIA] [\-\-extSIA] [\-\-extCP] [\-\-extPM] [\-\-extPC] [\-\-extIA] [\-\-extSKID]
|
||||
$ certutil \-S \-k rsa|dsa|ec \-n certname \-s subject [\-c issuer |\-x] \-t trustargs \-d directory [\-m serial\-number] [\-v valid\-months] [\-w offset\-months] [\-p phone] [\-1] [\-2] [\-3] [\-4] [\-5 keyword] [\-6 keyword] [\-7 emailAddress] [\-8 dns\-names] [\-\-extAIA] [\-\-extSIA] [\-\-extCP] [\-\-extPM] [\-\-extPC] [\-\-extIA] [\-\-extSKID]
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1348,7 +1442,7 @@ argument)\&. The issuing certificate must be in the certificate database in the
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-C \-c issuer \-i cert\-request\-file \-o output\-file [\-m serial\-number] [\-v valid\-months] [\-w offset\-months] \-d [sql:]directory [\-1] [\-2] [\-3] [\-4] [\-5 keyword] [\-6 keyword] [\-7 emailAddress] [\-8 dns\-names]
|
||||
certutil \-C \-c issuer \-i cert\-request\-file \-o output\-file [\-m serial\-number] [\-v valid\-months] [\-w offset\-months] \-d directory [\-1] [\-2] [\-3] [\-4] [\-5 keyword] [\-6 keyword] [\-7 emailAddress] [\-8 dns\-names]
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1360,7 +1454,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-C \-c "my\-ca\-cert" \-i /home/certs/cert\&.req \-o cert\&.cer \-m 010 \-v 12 \-w 1 \-d sql:$HOME/nssdb \-1 nonRepudiation,dataEncipherment \-5 sslClient \-6 clientAuth \-7 jsmith@example\&.com
|
||||
$ certutil \-C \-c "my\-ca\-cert" \-i /home/certs/cert\&.req \-o cert\&.cer \-m 010 \-v 12 \-w 1 \-d $HOME/nssdb \-1 nonRepudiation,dataEncipherment \-5 sslClient \-6 clientAuth \-7 jsmith@example\&.com
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1376,7 +1470,7 @@ command option lists all of the certificates listed in the certificate database\
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-L \-d sql:/home/my/sharednssdb
|
||||
$ certutil \-L \-d /home/my/sharednssdb
|
||||
|
||||
Certificate Nickname Trust Attributes
|
||||
SSL,S/MIME,JAR/XPI
|
||||
|
|
@ -1402,7 +1496,7 @@ argument prints the certificate in ASCII format:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-L \-d sql:$HOME/nssdb \-a \-n my\-ca\-cert
|
||||
$ certutil \-L \-d $HOME/nssdb \-a \-n my\-ca\-cert
|
||||
\-\-\-\-\-BEGIN CERTIFICATE\-\-\-\-\-
|
||||
MIIB1DCCAT2gAwIBAgICDkIwDQYJKoZIhvcNAQEFBQAwFTETMBEGA1UEAxMKRXhh
|
||||
bXBsZSBDQTAeFw0xMzAzMTMxOTEwMjlaFw0xMzA2MTMxOTEwMjlaMBUxEzARBgNV
|
||||
|
|
@ -1426,7 +1520,7 @@ For a human\-readable display
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-L \-d sql:$HOME/nssdb \-n my\-ca\-cert
|
||||
$ certutil \-L \-d $HOME/nssdb \-n my\-ca\-cert
|
||||
Certificate:
|
||||
Data:
|
||||
Version: 3 (0x2)
|
||||
|
|
@ -1509,7 +1603,7 @@ argument to give the path to the directory\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-K \-d sql:$HOME/nssdb
|
||||
$ certutil \-K \-d $HOME/nssdb
|
||||
certutil: Checking token "NSS Certificate DB" in slot "NSS User Private Key and Certificate Services "
|
||||
< 0> rsa 455a6673bde9375c2887ec8bf8016b3f9f35861d Thawte Freemail Member\*(Aqs Thawte Consulting (Pty) Ltd\&. ID
|
||||
< 1> rsa 40defeeb522ade11090eacebaaf1196a172127df Example Domain Administrator Cert
|
||||
|
|
@ -1575,7 +1669,7 @@ database\&. The path to the directory (\fB\-d\fR) is required\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-U \-d sql:/home/my/sharednssdb
|
||||
$ certutil \-U \-d /home/my/sharednssdb
|
||||
|
||||
slot: NSS User Private Key and Certificate Services
|
||||
token: NSS Certificate DB
|
||||
|
|
@ -1599,7 +1693,7 @@ command option\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-A \-n certname \-t trustargs \-d [sql:]directory [\-a] [\-i input\-file]
|
||||
certutil \-A \-n certname \-t trustargs \-d directory [\-a] [\-i input\-file]
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1611,7 +1705,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-A \-n "CN=My SSL Certificate" \-t ",," \-d sql:/home/my/sharednssdb \-i /home/example\-certs/cert\&.cer
|
||||
$ certutil \-A \-n "CN=My SSL Certificate" \-t ",," \-d /home/my/sharednssdb \-i /home/example\-certs/cert\&.cer
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1629,7 +1723,7 @@ command\&. The trust arguments for certificates have the format
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-E \-n "CN=John Smith Email Cert" \-t ",P," \-d sql:/home/my/sharednssdb \-i /home/example\-certs/email\&.cer
|
||||
$ certutil \-E \-n "CN=John Smith Email Cert" \-t ",P," \-d /home/my/sharednssdb \-i /home/example\-certs/email\&.cer
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1645,7 +1739,7 @@ option\&. The only required options are to give the security database directory
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-D \-d [sql:]directory \-n "nickname"
|
||||
certutil \-D \-d directory \-n "nickname"
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1657,7 +1751,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-D \-d sql:/home/my/sharednssdb \-n "my\-ssl\-cert"
|
||||
$ certutil \-D \-d /home/my/sharednssdb \-n "my\-ssl\-cert"
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1673,7 +1767,7 @@ command option\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-V \-n certificate\-name [\-b time] [\-e] [\-u cert\-usage] \-d [sql:]directory
|
||||
certutil \-V \-n certificate\-name [\-b time] [\-e] [\-u cert\-usage] \-d directory
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1685,7 +1779,7 @@ For example, to validate an email certificate:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-V \-n "John Smith\*(Aqs Email Cert" \-e \-u S,R \-d sql:/home/my/sharednssdb
|
||||
$ certutil \-V \-n "John Smith\*(Aqs Email Cert" \-e \-u S,R \-d /home/my/sharednssdb
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1699,7 +1793,7 @@ The trust settings (which relate to the operations that a certificate is allowed
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-M \-n certificate\-name \-t trust\-args \-d [sql:]directory
|
||||
certutil \-M \-n certificate\-name \-t trust\-args \-d directory
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1711,7 +1805,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-M \-n "My CA Certificate" \-d sql:/home/my/sharednssdb \-t "CT,CT,CT"
|
||||
$ certutil \-M \-n "My CA Certificate" \-d /home/my/sharednssdb \-t "CT,CT,CT"
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1729,7 +1823,7 @@ prints the full chain of a certificate, going from the initial CA (the root CA)
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-d sql:/home/my/sharednssdb \-O \-n "jsmith@example\&.com"
|
||||
$ certutil \-d /home/my/sharednssdb \-O \-n "jsmith@example\&.com"
|
||||
"Builtin Object Token:Thawte Personal Freemail CA" [E=personal\-freemail@thawte\&.com,CN=Thawte Personal Freemail CA,OU=Certification Services Division,O=Thawte Consulting,L=Cape Town,ST=Western Cape,C=ZA]
|
||||
|
||||
"Thawte Personal Freemail Issuing CA \- Thawte Consulting" [CN=Thawte Personal Freemail Issuing CA,O=Thawte Consulting (Pty) Ltd\&.,C=ZA]
|
||||
|
|
@ -1748,7 +1842,7 @@ The device which stores certificates \-\- both external hardware devices and int
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-T \-d [sql:]directory \-h token\-name \-0 security\-officer\-password
|
||||
certutil \-T \-d directory \-h token\-name \-0 security\-officer\-password
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1760,7 +1854,7 @@ Many networks have dedicated personnel who handle changes to security tokens (th
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-T \-d sql:/home/my/sharednssdb \-h nethsm \-0 secret
|
||||
$ certutil \-T \-d /home/my/sharednssdb \-h nethsm \-0 secret
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1785,7 +1879,7 @@ command must give information about the original database and then use the stand
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-\-upgrade\-merge \-d [sql:]directory [\-P dbprefix] \-\-source\-dir directory \-\-source\-prefix dbprefix \-\-upgrade\-id id \-\-upgrade\-token\-name name [\-@ password\-file]
|
||||
certutil \-\-upgrade\-merge \-d directory [\-P dbprefix] \-\-source\-dir directory \-\-source\-prefix dbprefix \-\-upgrade\-id id \-\-upgrade\-token\-name name [\-@ password\-file]
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1797,7 +1891,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-\-upgrade\-merge \-d sql:/home/my/sharednssdb \-\-source\-dir /opt/my\-app/alias/ \-\-source\-prefix serverapp\- \-\-upgrade\-id 1 \-\-upgrade\-token\-name internal
|
||||
$ certutil \-\-upgrade\-merge \-d /home/my/sharednssdb \-\-source\-dir /opt/my\-app/alias/ \-\-source\-prefix serverapp\- \-\-upgrade\-id 1 \-\-upgrade\-token\-name internal
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1811,7 +1905,7 @@ command only requires information about the location of the original database; s
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
certutil \-\-merge \-d [sql:]directory [\-P dbprefix] \-\-source\-dir directory \-\-source\-prefix dbprefix [\-@ password\-file]
|
||||
certutil \-\-merge \-d directory [\-P dbprefix] \-\-source\-dir directory \-\-source\-prefix dbprefix [\-@ password\-file]
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1823,7 +1917,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-\-merge \-d sql:/home/my/sharednssdb \-\-source\-dir /opt/my\-app/alias/ \-\-source\-prefix serverapp\-
|
||||
$ certutil \-\-merge \-d /home/my/sharednssdb \-\-source\-dir /opt/my\-app/alias/ \-\-source\-prefix serverapp\-
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1926,30 +2020,30 @@ database type\&. The shared database type is preferred; the legacy format is inc
|
|||
.PP
|
||||
By default, the tools (\fBcertutil\fR,
|
||||
\fBpk12util\fR,
|
||||
\fBmodutil\fR) assume that the given security databases follow the more common legacy type\&. Using the SQLite databases must be manually specified by using the
|
||||
\fBsql:\fR
|
||||
\fBmodutil\fR) assume that the given security databases use the SQLite type\&. Using the legacy databases must be manually specified by using the
|
||||
\fBdbm:\fR
|
||||
prefix with the given security directory\&. For example:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
$ certutil \-L \-d sql:/home/my/sharednssdb
|
||||
$ certutil \-L \-d dbm:/home/my/sharednssdb
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.PP
|
||||
To set the shared database type as the default type for the tools, set the
|
||||
To set the legacy database type as the default type for the tools, set the
|
||||
\fBNSS_DEFAULT_DB_TYPE\fR
|
||||
environment variable to
|
||||
\fBsql\fR:
|
||||
\fBdbm\fR:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
export NSS_DEFAULT_DB_TYPE="sql"
|
||||
export NSS_DEFAULT_DB_TYPE="dbm"
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1958,8 +2052,6 @@ export NSS_DEFAULT_DB_TYPE="sql"
|
|||
This line can be set added to the
|
||||
~/\&.bashrc
|
||||
file to make the change permanent\&.
|
||||
.PP
|
||||
Most applications do not use the shared database by default, but they can be configured to use them\&. For example, this how\-to article covers how to configure Firefox and Thunderbird to use the new shared NSS databases:
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: CRLUTIL
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
|
||||
.\" Date: 5 June 2014
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "CRLUTIL" "1" "5 June 2014" "nss-tools" "NSS Security Tools"
|
||||
.TH "CRLUTIL" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: DERDUMP
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.77.1 <http://docbook.sf.net/>
|
||||
.\" Date: 15 February 2013
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "DERDUMP" "1" "15 February 2013" "nss-tools" "NSS Security Tools"
|
||||
.TH "DERDUMP" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
@ -68,12 +68,12 @@ Mailing lists: pki\-devel@redhat\&.com and pki\-users@redhat\&.com
|
|||
IRC: Freenode at #dogtag\-pki
|
||||
.SH "AUTHORS"
|
||||
.PP
|
||||
The NSS tools were written and maintained by developers with Netscape and now with Red Hat\&.
|
||||
The NSS tools were written and maintained by developers with Netscape, Red Hat, Sun, Oracle, Mozilla, and Google\&.
|
||||
.PP
|
||||
Authors: Gerhardus Geldenhuis <gerhardus\&.geldenhuis@gmail\&.com>\&. Elio Maldonado <emaldona@redhat\&.com>, Deon Lackey <dlackey@redhat\&.com>
|
||||
.SH "LICENSE"
|
||||
.PP
|
||||
Licensed under the Mozilla Public License, version 1\&.1, and/or the GNU General Public License, version 2 or later, and/or the GNU Lesser General Public License, version 2\&.1 or later\&.
|
||||
Licensed under the Mozilla Public License, v\&. 2\&.0\&. If a copy of the MPL was not distributed with this file, You can obtain one at http://mozilla\&.org/MPL/2\&.0/\&.
|
||||
.SH "NOTES"
|
||||
.IP " 1." 4
|
||||
Mozilla NSS bug 836477
|
||||
|
|
|
|||
|
|
@ -2,12 +2,12 @@
|
|||
.\" Title: MODUTIL
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 5 October 2017
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "MODUTIL" "1" "5 October 2017" "nss-tools" "NSS Security Tools"
|
||||
.TH "MODUTIL" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
@ -188,18 +188,18 @@ Enable specific ciphers in a module that is being added to the database\&. The
|
|||
is a colon\-delimited list of cipher names\&. Enclose this list in quotation marks if it contains spaces\&.
|
||||
.RE
|
||||
.PP
|
||||
\-dbdir [sql:]directory
|
||||
\-dbdir directory
|
||||
.RS 4
|
||||
Specify the database directory in which to access or create security module database files\&.
|
||||
.sp
|
||||
\fBmodutil\fR
|
||||
supports two types of databases: the legacy security databases (cert8\&.db,
|
||||
key3\&.db, and
|
||||
secmod\&.db) and new SQLite databases (cert9\&.db,
|
||||
secmod\&.db) and SQLite databases (cert9\&.db,
|
||||
key4\&.db, and
|
||||
pkcs11\&.txt)\&. If the prefix
|
||||
\fBsql:\fR
|
||||
is not used, then the tool assumes that the given databases are in the old format\&.
|
||||
\fBdbm:\fR
|
||||
is not used, then the tool assumes that the given databases are in SQLite format\&.
|
||||
.RE
|
||||
.PP
|
||||
\-\-dbprefix prefix
|
||||
|
|
@ -207,7 +207,7 @@ is not used, then the tool assumes that the given databases are in the old forma
|
|||
Specify the prefix used on the database files, such as
|
||||
my_
|
||||
for
|
||||
my_cert8\&.db\&. This option is provided as a special case\&. Changing the names of the certificate and key databases is not recommended\&.
|
||||
my_cert9\&.db\&. This option is provided as a special case\&. Changing the names of the certificate and key databases is not recommended\&.
|
||||
.RE
|
||||
.PP
|
||||
\-installdir root\-installation\-directory
|
||||
|
|
@ -330,7 +330,7 @@ can be used to create these files\&. The only required argument is the database
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-create \-dbdir [sql:]directory
|
||||
modutil \-create \-dbdir directory
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -358,7 +358,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-dbdir sql:/home/my/sharednssdb \-add "Example PKCS #11 Module" \-libfile "/tmp/crypto\&.so" \-mechanisms RSA:DSA:RC2:RANDOM
|
||||
modutil \-dbdir /home/my/sharednssdb \-add "Example PKCS #11 Module" \-libfile "/tmp/crypto\&.so" \-mechanisms RSA:DSA:RC2:RANDOM
|
||||
|
||||
Using database directory \&.\&.\&.
|
||||
Module "Example PKCS #11 Module" added to database\&.
|
||||
|
|
@ -411,7 +411,7 @@ argument\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-dbdir sql:/home/mt"jar\-install\-filey/sharednssdb \-jar install\&.jar \-installdir sql:/home/my/sharednssdb
|
||||
modutil \-dbdir /home/mt"jar\-install\-filey/sharednssdb \-jar install\&.jar \-installdir /home/my/sharednssdb
|
||||
|
||||
This installation JAR file was signed by:
|
||||
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
|
||||
|
|
@ -473,7 +473,7 @@ database:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-delete modulename \-dbdir [sql:]directory
|
||||
modutil \-delete modulename \-dbdir directory
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -493,7 +493,7 @@ command\&.
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-list [modulename] \-dbdir [sql:]directory
|
||||
modutil \-list [modulename] \-dbdir directory
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -505,7 +505,7 @@ Listing the modules shows the module name, their status, and other associated se
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-list \-dbdir sql:/home/my/sharednssdb
|
||||
modutil \-list \-dbdir /home/my/sharednssdb
|
||||
|
||||
Listing of PKCS #11 Modules
|
||||
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
|
||||
|
|
@ -534,7 +534,7 @@ returns details information about the module itself, like supported cipher mecha
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-list "NSS Internal PKCS #11 Module" \-dbdir sql:/home/my/sharednssdb
|
||||
modutil \-list "NSS Internal PKCS #11 Module" \-dbdir /home/my/sharednssdb
|
||||
|
||||
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
|
||||
Name: NSS Internal PKCS #11 Module
|
||||
|
|
@ -594,7 +594,7 @@ command\&.)
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-rawlist \-dbdir sql:/home/my/sharednssdb
|
||||
modutil \-rawlist \-dbdir /home/my/sharednssdb
|
||||
name="NSS Internal PKCS #11 Module" parameters="configdir=\&. certPrefix= keyPrefix= secmod=secmod\&.db flags=readOnly " NSS="trustOrder=75 cipherOrder=100 slotParams={0x00000001=[slotFlags=RSA,RC4,RC2,DES,DH,SHA1,MD5,MD2,SSL,TLS,AES,RANDOM askpw=any timeout=30 ] } Flags=internal,critical"
|
||||
.fi
|
||||
.if n \{\
|
||||
|
|
@ -688,7 +688,7 @@ option\&. For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-fips true \-dbdir sql:/home/my/sharednssdb/
|
||||
modutil \-fips true \-dbdir /home/my/sharednssdb/
|
||||
|
||||
FIPS mode enabled\&.
|
||||
.fi
|
||||
|
|
@ -704,7 +704,7 @@ command with either a true or false flag (it doesn\*(Aqt matter which)\&. The to
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-chkfips false \-dbdir sql:/home/my/sharednssdb/
|
||||
modutil \-chkfips false \-dbdir /home/my/sharednssdb/
|
||||
|
||||
FIPS mode enabled\&.
|
||||
.fi
|
||||
|
|
@ -730,7 +730,7 @@ modutil \-changepw tokenname [\-pwfile old\-password\-file] [\-newpwfile new\-pa
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-dbdir sql:/home/my/sharednssdb \-changepw "NSS Certificate DB"
|
||||
modutil \-dbdir /home/my/sharednssdb \-changepw "NSS Certificate DB"
|
||||
|
||||
Enter old password:
|
||||
Incorrect password, try again\&.\&.\&.
|
||||
|
|
@ -1341,30 +1341,30 @@ database type\&. The shared database type is preferred; the legacy format is inc
|
|||
.PP
|
||||
By default, the tools (\fBcertutil\fR,
|
||||
\fBpk12util\fR,
|
||||
\fBmodutil\fR) assume that the given security databases follow the more common legacy type\&. Using the SQLite databases must be manually specified by using the
|
||||
\fBsql:\fR
|
||||
\fBmodutil\fR) assume that the given security databases use the SQLite type\&. Using the legacy databases must be manually specified by using the
|
||||
\fBdbm:\fR
|
||||
prefix with the given security directory\&. For example:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
modutil \-create \-dbdir sql:/home/my/sharednssdb
|
||||
modutil \-create \-dbdir dbm:/home/my/sharednssdb
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.PP
|
||||
To set the shared database type as the default type for the tools, set the
|
||||
To set the legacy database type as the default type for the tools, set the
|
||||
\fBNSS_DEFAULT_DB_TYPE\fR
|
||||
environment variable to
|
||||
\fBsql\fR:
|
||||
\fBdbm\fR:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
export NSS_DEFAULT_DB_TYPE="sql"
|
||||
export NSS_DEFAULT_DB_TYPE="dbm"
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -1373,8 +1373,6 @@ export NSS_DEFAULT_DB_TYPE="sql"
|
|||
This line can be added to the
|
||||
~/\&.bashrc
|
||||
file to make the change permanent for the user\&.
|
||||
.PP
|
||||
Most applications do not use the shared database by default, but they can be configured to use them\&. For example, this how\-to article covers how to configure Firefox and Thunderbird to use the new shared NSS databases:
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
|
|
|
|||
|
|
@ -2,12 +2,12 @@
|
|||
.\" Title: PK12UTIL
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 5 October 2017
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "PK12UTIL" "1" "5 October 2017" "nss-tools" "NSS Security Tools"
|
||||
.TH "PK12UTIL" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
@ -31,7 +31,7 @@
|
|||
pk12util \- Export and import keys and certificate to or from a PKCS #12 file and the NSS database
|
||||
.SH "SYNOPSIS"
|
||||
.HP \w'\fBpk12util\fR\ 'u
|
||||
\fBpk12util\fR [\-i\ p12File|\-l\ p12File|\-o\ p12File] [\-d\ [sql:]directory] [\-h\ tokenname] [\-P\ dbprefix] [\-r] [\-v] [\-k\ slotPasswordFile|\-K\ slotPassword] [\-w\ p12filePasswordFile|\-W\ p12filePassword]
|
||||
\fBpk12util\fR [\-i\ p12File|\-l\ p12File|\-o\ p12File] [\-c\ keyCipher] [\-C\ certCipher] [\-d\ directory] [\-h\ tokenname] [\-m\ |\ \-\-key\-len\ keyLength] [\-M\ hashAlg] [\-n\ certname] [\-P\ dbprefix] [\-r] [\-v] [\-\-cert\-key\-len\ certKeyLength] [\-k\ slotPasswordFile|\-K\ slotPassword] [\-w\ p12filePasswordFile|\-W\ p12filePassword]
|
||||
.SH "STATUS"
|
||||
.PP
|
||||
This documentation is still work in progress\&. Please contribute to the initial review in
|
||||
|
|
@ -71,7 +71,7 @@ Specify the key encryption algorithm\&.
|
|||
Specify the certiticate encryption algorithm\&.
|
||||
.RE
|
||||
.PP
|
||||
\-d [sql:]directory
|
||||
\-d directory
|
||||
.RS 4
|
||||
Specify the database directory into which to import to or export from certificates and keys\&.
|
||||
.sp
|
||||
|
|
@ -81,8 +81,8 @@ key3\&.db, and
|
|||
secmod\&.db) and new SQLite databases (cert9\&.db,
|
||||
key4\&.db, and
|
||||
pkcs11\&.txt)\&. If the prefix
|
||||
\fBsql:\fR
|
||||
is not used, then the tool assumes that the given databases are in the old format\&.
|
||||
\fBdbm:\fR
|
||||
is not used, then the tool assumes that the given databases are in the SQLite format\&.
|
||||
.RE
|
||||
.PP
|
||||
\-h tokenname
|
||||
|
|
@ -105,7 +105,12 @@ Specify the slot\*(Aqs password\&.
|
|||
Specify the desired length of the symmetric key to be used to encrypt the private key\&.
|
||||
.RE
|
||||
.PP
|
||||
\-n | \-\-cert\-key\-len certKeyLength
|
||||
\-M hashAlg
|
||||
.RS 4
|
||||
Specify the hash algorithm used in the pkcs #12 mac\&. This algorithm also specifies the HMAC used in the prf when using pkcs #5 v2\&.
|
||||
.RE
|
||||
.PP
|
||||
\-\-cert\-key\-len certKeyLength
|
||||
.RS 4
|
||||
Specify the desired length of the symmetric key to be used to encrypt the certificates and other meta\-data\&.
|
||||
.RE
|
||||
|
|
@ -440,7 +445,7 @@ for a directory or
|
|||
\fB\-h\fR
|
||||
for a token)\&.
|
||||
.PP
|
||||
pk12util \-i p12File [\-h tokenname] [\-v] [\-d [sql:]directory] [\-P dbprefix] [\-k slotPasswordFile|\-K slotPassword] [\-w p12filePasswordFile|\-W p12filePassword]
|
||||
pk12util \-i p12File [\-h tokenname] [\-v] [\-d directory] [\-P dbprefix] [\-k slotPasswordFile|\-K slotPassword] [\-w p12filePasswordFile|\-W p12filePassword]
|
||||
.PP
|
||||
For example:
|
||||
.PP
|
||||
|
|
@ -450,7 +455,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
# pk12util \-i /tmp/cert\-files/users\&.p12 \-d sql:/home/my/sharednssdb
|
||||
# pk12util \-i /tmp/cert\-files/users\&.p12 \-d /home/my/sharednssdb
|
||||
|
||||
Enter a password which will be used to encrypt your keys\&.
|
||||
The password should be at least 8 characters long,
|
||||
|
|
@ -471,7 +476,7 @@ Using the
|
|||
\fBpk12util\fR
|
||||
command to export certificates and keys requires both the name of the certificate to extract from the database (\fB\-n\fR) and the PKCS #12\-formatted output file to write to\&. There are optional parameters that can be used to encrypt the file to protect the certificate material\&.
|
||||
.PP
|
||||
pk12util \-o p12File \-n certname [\-c keyCipher] [\-C certCipher] [\-m|\-\-key_len keyLen] [\-n|\-\-cert_key_len certKeyLen] [\-d [sql:]directory] [\-P dbprefix] [\-k slotPasswordFile|\-K slotPassword] [\-w p12filePasswordFile|\-W p12filePassword]
|
||||
pk12util \-o p12File \-n certname [\-c keyCipher] [\-C certCipher] [\-m|\-\-key_len keyLen] [\-n|\-\-cert_key_len certKeyLen] [\-d directory] [\-P dbprefix] [\-k slotPasswordFile|\-K slotPassword] [\-w p12filePasswordFile|\-W p12filePassword]
|
||||
.PP
|
||||
For example:
|
||||
.sp
|
||||
|
|
@ -479,7 +484,7 @@ For example:
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
# pk12util \-o certs\&.p12 \-n Server\-Cert \-d sql:/home/my/sharednssdb
|
||||
# pk12util \-o certs\&.p12 \-n Server\-Cert \-d /home/my/sharednssdb
|
||||
Enter password for PKCS12 file:
|
||||
Re\-enter password:
|
||||
.fi
|
||||
|
|
@ -495,7 +500,7 @@ file are not human\-readable\&. The certificates and keys in the file can be pri
|
|||
\&.p12
|
||||
file\&.
|
||||
.PP
|
||||
pk12util \-l p12File [\-h tokenname] [\-r] [\-d [sql:]directory] [\-P dbprefix] [\-k slotPasswordFile|\-K slotPassword] [\-w p12filePasswordFile|\-W p12filePassword]
|
||||
pk12util \-l p12File [\-h tokenname] [\-r] [\-d directory] [\-P dbprefix] [\-k slotPasswordFile|\-K slotPassword] [\-w p12filePasswordFile|\-W p12filePassword]
|
||||
.PP
|
||||
For example, this prints the default ASCII output:
|
||||
.sp
|
||||
|
|
@ -737,30 +742,30 @@ database type\&. The shared database type is preferred; the legacy format is inc
|
|||
.PP
|
||||
By default, the tools (\fBcertutil\fR,
|
||||
\fBpk12util\fR,
|
||||
\fBmodutil\fR) assume that the given security databases follow the more common legacy type\&. Using the SQLite databases must be manually specified by using the
|
||||
\fBsql:\fR
|
||||
\fBmodutil\fR) assume that the given security databases use the SQLite type Using the legacy databases must be manually specified by using the
|
||||
\fBdbm:\fR
|
||||
prefix with the given security directory\&. For example:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
# pk12util \-i /tmp/cert\-files/users\&.p12 \-d sql:/home/my/sharednssdb
|
||||
# pk12util \-i /tmp/cert\-files/users\&.p12 \-d dbm:/home/my/sharednssdb
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.PP
|
||||
To set the shared database type as the default type for the tools, set the
|
||||
To set the legacy database type as the default type for the tools, set the
|
||||
\fBNSS_DEFAULT_DB_TYPE\fR
|
||||
environment variable to
|
||||
\fBsql\fR:
|
||||
\fBdbm\fR:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
export NSS_DEFAULT_DB_TYPE="sql"
|
||||
export NSS_DEFAULT_DB_TYPE="dbm"
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -769,8 +774,6 @@ export NSS_DEFAULT_DB_TYPE="sql"
|
|||
This line can be set added to the
|
||||
~/\&.bashrc
|
||||
file to make the change permanent\&.
|
||||
.PP
|
||||
Most applications do not use the shared database by default, but they can be configured to use them\&. For example, this how\-to article covers how to configure Firefox and Thunderbird to use the new shared NSS databases:
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: PP
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
|
||||
.\" Date: 29 July 2014
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "PP" "1" "29 July 2014" "nss-tools" "NSS Security Tools"
|
||||
.TH "PP" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
@ -38,12 +38,12 @@ This documentation is still work in progress\&. Please contribute to the initial
|
|||
\m[blue]\fBMozilla NSS bug 836477\fR\m[]\&\s-2\u[1]\d\s+2
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
\fBpp \fRpretty\-prints private and public key, certificate, certificate\-request, pkcs7 or crl files
|
||||
\fBpp \fRpretty\-prints private and public key, certificate, certificate\-request, pkcs7, pkcs12 or crl files
|
||||
.SH "OPTIONS"
|
||||
.PP
|
||||
\fB\-t \fR \fItype\fR
|
||||
.RS 4
|
||||
specify the input, one of {private\-key | public\-key | certificate | certificate\-request | pkcs7 | crl}
|
||||
specify the input, one of {private\-key | public\-key | certificate | certificate\-request | pkcs7 | pkcs12 | crl | name}
|
||||
.sp
|
||||
.RE
|
||||
.PP
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: signtool
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
|
||||
.\" Date: 5 June 2014
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "SIGNTOOL" "1" "5 June 2014" "nss-tools" "NSS Security Tools"
|
||||
.TH "SIGNTOOL" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: SIGNVER
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
|
||||
.\" Date: 5 June 2014
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "SIGNVER" "1" "5 June 2014" "nss-tools" "NSS Security Tools"
|
||||
.TH "SIGNVER" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
@ -52,7 +52,7 @@ Displays all of the information in the PKCS#7 signature\&.
|
|||
Verifies the digital signature\&.
|
||||
.RE
|
||||
.PP
|
||||
\-d [sql:]\fIdirectory\fR
|
||||
\-d \fIdirectory\fR
|
||||
.RS 4
|
||||
Specify the database directory which contains the certificates and keys\&.
|
||||
.sp
|
||||
|
|
@ -62,8 +62,8 @@ key3\&.db, and
|
|||
secmod\&.db) and new SQLite databases (cert9\&.db,
|
||||
key4\&.db, and
|
||||
pkcs11\&.txt)\&. If the prefix
|
||||
\fBsql:\fR
|
||||
is not used, then the tool assumes that the given databases are in the old format\&.
|
||||
\fBdbm:\fR
|
||||
is not used, then the tool assumes that the given databases are in the SQLite format\&.
|
||||
.RE
|
||||
.PP
|
||||
\-a
|
||||
|
|
@ -101,7 +101,7 @@ option verifies that the signature in a given signature file is valid when used
|
|||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
signver \-V \-s \fIsignature_file\fR \-i \fIsigned_file\fR \-d sql:/home/my/sharednssdb
|
||||
signver \-V \-s \fIsignature_file\fR \-i \fIsigned_file\fR \-d /home/my/sharednssdb
|
||||
|
||||
signatureValid=yes
|
||||
.fi
|
||||
|
|
@ -207,30 +207,30 @@ database type\&. The shared database type is preferred; the legacy format is inc
|
|||
.PP
|
||||
By default, the tools (\fBcertutil\fR,
|
||||
\fBpk12util\fR,
|
||||
\fBmodutil\fR) assume that the given security databases follow the more common legacy type\&. Using the SQLite databases must be manually specified by using the
|
||||
\fBsql:\fR
|
||||
\fBmodutil\fR) assume that the given security databases use the SQLite type Using the legacy databases must be manually specified by using the
|
||||
\fBdbm:\fR
|
||||
prefix with the given security directory\&. For example:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
# signver \-A \-s \fIsignature\fR \-d sql:/home/my/sharednssdb
|
||||
# signver \-A \-s \fIsignature\fR \-d dbm:/home/my/sharednssdb
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
.\}
|
||||
.PP
|
||||
To set the shared database type as the default type for the tools, set the
|
||||
To set the legacy database type as the default type for the tools, set the
|
||||
\fBNSS_DEFAULT_DB_TYPE\fR
|
||||
environment variable to
|
||||
\fBsql\fR:
|
||||
\fBdbm\fR:
|
||||
.sp
|
||||
.if n \{\
|
||||
.RS 4
|
||||
.\}
|
||||
.nf
|
||||
export NSS_DEFAULT_DB_TYPE="sql"
|
||||
export NSS_DEFAULT_DB_TYPE="dbm"
|
||||
.fi
|
||||
.if n \{\
|
||||
.RE
|
||||
|
|
@ -239,8 +239,6 @@ export NSS_DEFAULT_DB_TYPE="sql"
|
|||
This line can be added to the
|
||||
~/\&.bashrc
|
||||
file to make the change permanent for the user\&.
|
||||
.PP
|
||||
Most applications do not use the shared database by default, but they can be configured to use them\&. For example, this how\-to article covers how to configure Firefox and Thunderbird to use the new shared NSS databases:
|
||||
.sp
|
||||
.RS 4
|
||||
.ie n \{\
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: SSLTAP
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
|
||||
.\" Date: 5 June 2014
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "SSLTAP" "1" "5 June 2014" "nss-tools" "NSS Security Tools"
|
||||
.TH "SSLTAP" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: VFYCHAIN
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
|
||||
.\" Date: 5 June 2014
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "VFYCHAIN" "1" "5 June 2014" "nss-tools" "NSS Security Tools"
|
||||
.TH "VFYCHAIN" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,13 +1,13 @@
|
|||
'\" t
|
||||
.\" Title: VFYSERV
|
||||
.\" Author: [see the "Authors" section]
|
||||
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
|
||||
.\" Date: 5 June 2014
|
||||
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
|
||||
.\" Date: 19 May 2021
|
||||
.\" Manual: NSS Security Tools
|
||||
.\" Source: nss-tools
|
||||
.\" Language: English
|
||||
.\"
|
||||
.TH "VFYSERV" "1" "5 June 2014" "nss-tools" "NSS Security Tools"
|
||||
.TH "VFYSERV" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
|
||||
.\" -----------------------------------------------------------------
|
||||
.\" * Define some portability stuff
|
||||
.\" -----------------------------------------------------------------
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue