certutil.1 (50178B)
1 '\" t 2 .\" Title: CERTUTIL 3 .\" Author: [see the "Authors" section] 4 .\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/> 5 .\" Date: 19 May 2021 6 .\" Manual: NSS Security Tools 7 .\" Source: nss-tools 8 .\" Language: English 9 .\" 10 .TH "CERTUTIL" "1" "19 May 2021" "nss-tools" "NSS Security Tools" 11 .\" ----------------------------------------------------------------- 12 .\" * Define some portability stuff 13 .\" ----------------------------------------------------------------- 14 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 15 .\" http://bugs.debian.org/507673 16 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html 17 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 18 .ie \n(.g .ds Aq \(aq 19 .el .ds Aq ' 20 .\" ----------------------------------------------------------------- 21 .\" * set default formatting 22 .\" ----------------------------------------------------------------- 23 .\" disable hyphenation 24 .nh 25 .\" disable justification (adjust text to left margin only) 26 .ad l 27 .\" ----------------------------------------------------------------- 28 .\" * MAIN CONTENT STARTS HERE * 29 .\" ----------------------------------------------------------------- 30 .SH "NAME" 31 certutil \- Manage keys and certificate in both NSS databases and other NSS tokens 32 .SH "SYNOPSIS" 33 .HP \w'\fBcertutil\fR\ 'u 34 \fBcertutil\fR [\fIoptions\fR] [[\fIarguments\fR]] 35 .SH "STATUS" 36 .PP 37 This documentation is still work in progress\&. Please contribute to the initial review in 38 \m[blue]\fBMozilla NSS bug 836477\fR\m[]\&\s-2\u[1]\d\s+2 39 .SH "DESCRIPTION" 40 .PP 41 The Certificate Database Tool, 42 \fBcertutil\fR, is a command\-line utility that can create and modify certificate and key databases\&. It can specifically list, generate, modify, or delete certificates, create or change the password, generate new public and private key pairs, display the contents of the key database, or delete key pairs within the key database\&. 43 .PP 44 Certificate issuance, part of the key and certificate management process, requires that keys and certificates be created in the key database\&. This document discusses certificate and key database management\&. For information on the security module database management, see the 45 \fBmodutil\fR 46 manpage\&. 47 .SH "COMMAND OPTIONS AND ARGUMENTS" 48 .PP 49 Running 50 \fBcertutil\fR 51 always requires one and only one command option to specify the type of certificate operation\&. Each command option may take zero or more arguments\&. The command option 52 \fB\-H\fR 53 will list all the command options and their relevant arguments\&. 54 .PP 55 \fBCommand Options\fR 56 .PP 57 \-A 58 .RS 4 59 Add an existing certificate to a certificate database\&. The certificate database should already exist; if one is not present, this command option will initialize one by default\&. 60 .RE 61 .PP 62 \-B 63 .RS 4 64 Run a series of commands from the specified batch file\&. This requires the 65 \fB\-i\fR 66 argument\&. 67 .RE 68 .PP 69 \-C 70 .RS 4 71 Create a new binary certificate file from a binary certificate request file\&. Use the 72 \fB\-i\fR 73 argument to specify the certificate request file\&. If this argument is not used, 74 \fBcertutil\fR 75 prompts for a filename\&. 76 .RE 77 .PP 78 \-D 79 .RS 4 80 Delete a certificate from the certificate database\&. 81 .RE 82 .PP 83 \-\-rename 84 .RS 4 85 Change the database nickname of a certificate\&. 86 .RE 87 .PP 88 \-E 89 .RS 4 90 Add an email certificate to the certificate database\&. 91 .RE 92 .PP 93 \-F 94 .RS 4 95 Delete a private key and the associated certificate from a database\&. Specify the key to delete with the \-n argument or the \-k argument\&. Specify the database from which to delete the key with the 96 \fB\-d\fR 97 argument\&. 98 .sp 99 Some smart cards do not let you remove a public key you have generated\&. In such a case, only the private key is deleted from the key pair\&. 100 .RE 101 .PP 102 \-G 103 .RS 4 104 Generate a new public and private key pair within a key database\&. The key database should already exist; if one is not present, this command option will initialize one by default\&. Some smart cards can store only one key pair\&. If you create a new key pair for such a card, the previous pair is overwritten\&. 105 .RE 106 .PP 107 \-H 108 .RS 4 109 Display a list of the command options and arguments\&. 110 .RE 111 .PP 112 \-K 113 .RS 4 114 List the key ID of keys in the key database\&. A key ID is the modulus of the RSA key or the publicValue of the DSA key\&. IDs are displayed in hexadecimal ("0x" is not shown)\&. 115 .RE 116 .PP 117 \-L 118 .RS 4 119 List all the certificates, or display information about a named certificate, in a certificate database\&. Use the \-h tokenname argument to specify the certificate database on a particular hardware or software token\&. 120 .RE 121 .PP 122 \-M 123 .RS 4 124 Modify a certificate\*(Aqs trust attributes using the values of the \-t argument\&. 125 .RE 126 .PP 127 \-N 128 .RS 4 129 Create new certificate and key databases\&. 130 .RE 131 .PP 132 \-O 133 .RS 4 134 Print the certificate chain\&. 135 .RE 136 .PP 137 \-R 138 .RS 4 139 Create a certificate request file that can be submitted to a Certificate Authority (CA) for processing into a finished certificate\&. Output defaults to standard out unless you use \-o output\-file argument\&. Use the \-a argument to specify ASCII output\&. 140 .RE 141 .PP 142 \-S 143 .RS 4 144 Create an individual certificate and add it to a certificate database\&. 145 .RE 146 .PP 147 \-T 148 .RS 4 149 Reset the key database or token\&. 150 .RE 151 .PP 152 \-U 153 .RS 4 154 List all available modules or print a single named module\&. 155 .RE 156 .PP 157 \-V 158 .RS 4 159 Check the validity of a certificate and its attributes\&. 160 .RE 161 .PP 162 \-W 163 .RS 4 164 Change the password to a key database\&. 165 .RE 166 .PP 167 \-\-merge 168 .RS 4 169 Merge two databases into one\&. 170 .RE 171 .PP 172 \-\-upgrade\-merge 173 .RS 4 174 Upgrade an old database and merge it into a new database\&. This is used to migrate legacy NSS databases (cert8\&.db 175 and 176 key3\&.db) into the newer SQLite databases (cert9\&.db 177 and 178 key4\&.db)\&. 179 .RE 180 .PP 181 \fBArguments\fR 182 .PP 183 Arguments modify a command option and are usually lower case, numbers, or symbols\&. 184 .PP 185 \-a 186 .RS 4 187 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\&. 188 .RE 189 .PP 190 \-\-simple\-self\-signed 191 .RS 4 192 When printing the certificate chain, don\*(Aqt search for a chain if issuer name equals to subject name\&. 193 .RE 194 .PP 195 \-b validity\-time 196 .RS 4 197 Specify a time at which a certificate is required to be valid\&. Use when checking certificate validity with the 198 \fB\-V\fR 199 option\&. The format of the 200 \fIvalidity\-time\fR 201 argument is 202 \fIYYMMDDHHMMSS[+HHMM|\-HHMM|Z]\fR, which allows offsets to be set relative to the validity end time\&. Specifying seconds (\fISS\fR) is optional\&. When specifying an explicit time, use a Z at the end of the term, 203 \fIYYMMDDHHMMSSZ\fR, to close it\&. When specifying an offset time, use 204 \fIYYMMDDHHMMSS+HHMM\fR 205 or 206 \fIYYMMDDHHMMSS\-HHMM\fR 207 for adding or subtracting time, respectively\&. 208 .sp 209 If this option is not used, the validity check defaults to the current system time\&. 210 .RE 211 .PP 212 \-c issuer 213 .RS 4 214 Identify the certificate of the CA from which a new certificate will derive its authenticity\&. Use the exact nickname or alias of the CA certificate, or use the CA\*(Aqs email address\&. Bracket the issuer string with quotation marks if it contains spaces\&. 215 .RE 216 .PP 217 \-d [prefix]directory 218 .RS 4 219 Specify the database directory containing the certificate and key database files\&. 220 .sp 221 \fBcertutil\fR 222 supports two types of databases: the legacy security databases (cert8\&.db, 223 key3\&.db, and 224 secmod\&.db) and new SQLite databases (cert9\&.db, 225 key4\&.db, and 226 pkcs11\&.txt)\&. 227 .sp 228 NSS recognizes the following prefixes: 229 .sp 230 .RS 4 231 .ie n \{\ 232 \h'-04'\(bu\h'+03'\c 233 .\} 234 .el \{\ 235 .sp -1 236 .IP \(bu 2.3 237 .\} 238 \fBsql:\fR 239 requests the newer database 240 .RE 241 .sp 242 .RS 4 243 .ie n \{\ 244 \h'-04'\(bu\h'+03'\c 245 .\} 246 .el \{\ 247 .sp -1 248 .IP \(bu 2.3 249 .\} 250 \fBdbm:\fR 251 requests the legacy database 252 .RE 253 .sp 254 If no prefix is specified the default type is retrieved from NSS_DEFAULT_DB_TYPE\&. If NSS_DEFAULT_DB_TYPE is not set then 255 \fBsql:\fR 256 is the default\&. 257 .RE 258 .PP 259 \-\-dump\-ext\-val OID 260 .RS 4 261 For single cert, print binary DER encoding of extension OID\&. 262 .RE 263 .PP 264 \-e 265 .RS 4 266 Check a certificate\*(Aqs signature during the process of validating a certificate\&. 267 .RE 268 .PP 269 \-\-email email\-address 270 .RS 4 271 Specify the email address of a certificate to list\&. Used with the \-L command option\&. 272 .RE 273 .PP 274 \-\-extGeneric OID:critical\-flag:filename[,OID:critical\-flag:filename]\&.\&.\&. 275 .RS 4 276 Add one or multiple extensions that certutil cannot encode yet, by loading their encodings from external files\&. 277 .sp 278 .RS 4 279 .ie n \{\ 280 \h'-04'\(bu\h'+03'\c 281 .\} 282 .el \{\ 283 .sp -1 284 .IP \(bu 2.3 285 .\} 286 OID (example): 1\&.2\&.3\&.4 287 .RE 288 .sp 289 .RS 4 290 .ie n \{\ 291 \h'-04'\(bu\h'+03'\c 292 .\} 293 .el \{\ 294 .sp -1 295 .IP \(bu 2.3 296 .\} 297 critical\-flag: critical or not\-critical 298 .RE 299 .sp 300 .RS 4 301 .ie n \{\ 302 \h'-04'\(bu\h'+03'\c 303 .\} 304 .el \{\ 305 .sp -1 306 .IP \(bu 2.3 307 .\} 308 filename: full path to a file containing an encoded extension 309 .RE 310 .RE 311 .PP 312 \-f password\-file 313 .RS 4 314 Specify a file that will automatically supply the password to include in a certificate or to access a certificate database\&. This is a plain\-text file containing one password\&. Be sure to prevent unauthorized access to this file\&. 315 .RE 316 .PP 317 \-g keysize 318 .RS 4 319 Set a key size to use when generating new public and private key pairs\&. The minimum is 512 bits and the maximum is 16384 bits\&. The default is 2048 bits\&. Any size between the minimum and maximum is allowed\&. 320 .RE 321 .PP 322 \-h tokenname 323 .RS 4 324 Specify the name of a token to use or act on\&. If not specified the default token is the internal database slot\&. 325 .sp 326 The name can also be a PKCS #11 URI\&. For example, the NSS internal certificate store can be unambiguously specified as "pkcs11:token=NSS%20Certificate%20DB"\&. For details about the format, see RFC 7512\&. 327 .RE 328 .PP 329 \-i input_file 330 .RS 4 331 Pass an input file to the command\&. Depending on the command option, an input file can be a specific certificate, a certificate request file, or a batch file of commands\&. 332 .RE 333 .PP 334 \-k key\-type\-or\-id 335 .RS 4 336 Specify the type or specific ID of a key\&. 337 .sp 338 The valid key type options are rsa, dsa, ec, or all\&. The default value is rsa\&. Specifying the type of key can avoid mistakes caused by duplicate nicknames\&. Giving a key type generates a new key pair; giving the ID of an existing key reuses that key pair (which is required to renew certificates)\&. 339 .RE 340 .PP 341 \-l 342 .RS 4 343 Display detailed information when validating a certificate with the \-V option\&. 344 .RE 345 .PP 346 \-m serial\-number 347 .RS 4 348 Assign a unique serial number to a certificate being created\&. This operation should be performed by a CA\&. If no serial number is provided a default serial number is made from the current time\&. Serial numbers are limited to integers 349 .RE 350 .PP 351 \-n nickname 352 .RS 4 353 Specify the nickname of a certificate or key to list, create, add to a database, modify, or validate\&. Bracket the nickname string with quotation marks if it contains spaces\&. 354 .sp 355 The nickname can also be a PKCS #11 URI\&. For example, if you have a certificate named "my\-server\-cert" on the internal certificate store, it can be unambiguously specified as "pkcs11:token=NSS%20Certificate%20DB;object=my\-server\-cert"\&. For details about the format, see RFC 7512\&. 356 .RE 357 .PP 358 \-o output\-file 359 .RS 4 360 Specify the output file name for new certificates or binary certificate requests\&. Bracket the output\-file string with quotation marks if it contains spaces\&. If this argument is not used the output destination defaults to standard output\&. 361 .RE 362 .PP 363 \-P dbPrefix 364 .RS 4 365 Specify the prefix used on the certificate and key database file\&. This argument is provided to support legacy servers\&. Most applications do not use a database prefix\&. 366 .RE 367 .PP 368 \-p phone 369 .RS 4 370 Specify a contact telephone number to include in new certificates or certificate requests\&. Bracket this string with quotation marks if it contains spaces\&. 371 .RE 372 .PP 373 \-q pqgfile or curve\-name 374 .RS 4 375 Read an alternate PQG value from the specified file when generating DSA key pairs\&. If this argument is not used, 376 \fBcertutil\fR 377 generates its own PQG value\&. PQG files are created with a separate DSA utility\&. 378 .sp 379 Elliptic curve name is one of the ones from nistp256, nistp384, nistp521, curve25519\&. 380 .sp 381 If a token is available that supports more curves, the foolowing curves are supported as well: sect163k1, nistk163, sect163r1, sect163r2, nistb163, sect193r1, sect193r2, sect233k1, nistk233, sect233r1, nistb233, sect239k1, sect283k1, nistk283, sect283r1, nistb283, sect409k1, nistk409, sect409r1, nistb409, sect571k1, nistk571, sect571r1, nistb571, secp160k1, secp160r1, secp160r2, secp192k1, secp192r1, nistp192, secp224k1, secp224r1, nistp224, secp256k1, secp256r1, secp384r1, secp521r1, prime192v1, prime192v2, prime192v3, prime239v1, prime239v2, prime239v3, c2pnb163v1, c2pnb163v2, c2pnb163v3, c2pnb176v1, c2tnb191v1, c2tnb191v2, c2tnb191v3, c2pnb208w1, c2tnb239v1, c2tnb239v2, c2tnb239v3, c2pnb272w1, c2pnb304w1, c2tnb359w1, c2pnb368w1, c2tnb431r1, secp112r1, secp112r2, secp128r1, secp128r2, sect113r1, sect113r2, sect131r1, sect131r2 382 .RE 383 .PP 384 \-r 385 .RS 4 386 Display a certificate\*(Aqs binary DER encoding when listing information about that certificate with the \-L option\&. 387 .RE 388 .PP 389 \-s subject 390 .RS 4 391 Identify a particular certificate owner for new certificates or certificate requests\&. Bracket this string with quotation marks if it contains spaces\&. The subject identification format follows RFC #1485\&. 392 .RE 393 .PP 394 \-t trustargs 395 .RS 4 396 Specify the trust attributes to modify in an existing certificate or to apply to a certificate when creating it or adding it to a database\&. There are three available trust categories for each certificate, expressed in the order 397 \fISSL, email, object signing\fR 398 for each trust setting\&. In each category position, use none, any, or all of the attribute codes: 399 .sp 400 .RS 4 401 .ie n \{\ 402 \h'-04'\(bu\h'+03'\c 403 .\} 404 .el \{\ 405 .sp -1 406 .IP \(bu 2.3 407 .\} 408 \fBp\fR 409 \- Valid peer 410 .RE 411 .sp 412 .RS 4 413 .ie n \{\ 414 \h'-04'\(bu\h'+03'\c 415 .\} 416 .el \{\ 417 .sp -1 418 .IP \(bu 2.3 419 .\} 420 \fBP\fR 421 \- Trusted peer (implies p) 422 .RE 423 .sp 424 .RS 4 425 .ie n \{\ 426 \h'-04'\(bu\h'+03'\c 427 .\} 428 .el \{\ 429 .sp -1 430 .IP \(bu 2.3 431 .\} 432 \fBc\fR 433 \- Valid CA 434 .RE 435 .sp 436 .RS 4 437 .ie n \{\ 438 \h'-04'\(bu\h'+03'\c 439 .\} 440 .el \{\ 441 .sp -1 442 .IP \(bu 2.3 443 .\} 444 \fBC\fR 445 \- Trusted CA (implies c) 446 .RE 447 .sp 448 .RS 4 449 .ie n \{\ 450 \h'-04'\(bu\h'+03'\c 451 .\} 452 .el \{\ 453 .sp -1 454 .IP \(bu 2.3 455 .\} 456 \fBT\fR 457 \- trusted CA for client authentication (ssl server only) 458 .RE 459 .sp 460 The attribute codes for the categories are separated by commas, and the entire set of attributes enclosed by quotation marks\&. For example: 461 .sp 462 \fB\-t "TC,C,T"\fR 463 .sp 464 Use the \-L option to see a list of the current certificates and trust attributes in a certificate database\&. 465 .sp 466 Note that the output of the \-L option may include "u" flag, which means that there is a private key associated with the certificate\&. It is a dynamic flag and you cannot set it with certutil\&. 467 .RE 468 .PP 469 \-u certusage 470 .RS 4 471 Specify a usage context to apply when validating a certificate with the \-V option\&. 472 .sp 473 The contexts are the following: 474 .sp 475 .RS 4 476 .ie n \{\ 477 \h'-04'\(bu\h'+03'\c 478 .\} 479 .el \{\ 480 .sp -1 481 .IP \(bu 2.3 482 .\} 483 \fBC\fR 484 (as an SSL client) 485 .RE 486 .sp 487 .RS 4 488 .ie n \{\ 489 \h'-04'\(bu\h'+03'\c 490 .\} 491 .el \{\ 492 .sp -1 493 .IP \(bu 2.3 494 .\} 495 \fBV\fR 496 (as an SSL server) 497 .RE 498 .sp 499 .RS 4 500 .ie n \{\ 501 \h'-04'\(bu\h'+03'\c 502 .\} 503 .el \{\ 504 .sp -1 505 .IP \(bu 2.3 506 .\} 507 \fBL\fR 508 (as an SSL CA) 509 .RE 510 .sp 511 .RS 4 512 .ie n \{\ 513 \h'-04'\(bu\h'+03'\c 514 .\} 515 .el \{\ 516 .sp -1 517 .IP \(bu 2.3 518 .\} 519 \fBA\fR 520 (as Any CA) 521 .RE 522 .sp 523 .RS 4 524 .ie n \{\ 525 \h'-04'\(bu\h'+03'\c 526 .\} 527 .el \{\ 528 .sp -1 529 .IP \(bu 2.3 530 .\} 531 \fBY\fR 532 (Verify CA) 533 .RE 534 .sp 535 .RS 4 536 .ie n \{\ 537 \h'-04'\(bu\h'+03'\c 538 .\} 539 .el \{\ 540 .sp -1 541 .IP \(bu 2.3 542 .\} 543 \fBS\fR 544 (as an email signer) 545 .RE 546 .sp 547 .RS 4 548 .ie n \{\ 549 \h'-04'\(bu\h'+03'\c 550 .\} 551 .el \{\ 552 .sp -1 553 .IP \(bu 2.3 554 .\} 555 \fBR\fR 556 (as an email recipient) 557 .RE 558 .sp 559 .RS 4 560 .ie n \{\ 561 \h'-04'\(bu\h'+03'\c 562 .\} 563 .el \{\ 564 .sp -1 565 .IP \(bu 2.3 566 .\} 567 \fBO\fR 568 (as an OCSP status responder) 569 .RE 570 .sp 571 .RS 4 572 .ie n \{\ 573 \h'-04'\(bu\h'+03'\c 574 .\} 575 .el \{\ 576 .sp -1 577 .IP \(bu 2.3 578 .\} 579 \fBJ\fR 580 (as an object signer) 581 .RE 582 .sp 583 .RS 4 584 .ie n \{\ 585 \h'-04'\(bu\h'+03'\c 586 .\} 587 .el \{\ 588 .sp -1 589 .IP \(bu 2.3 590 .\} 591 \fBI\fR 592 (as an IPSEC user) 593 .RE 594 .RE 595 .PP 596 \-v valid\-months 597 .RS 4 598 Set the number of months a new certificate will be valid\&. The validity period begins at the current system time unless an offset is added or subtracted with the 599 \fB\-w\fR 600 option\&. If this argument is not used, the default validity period is three months\&. 601 .RE 602 .PP 603 \-w offset\-months 604 .RS 4 605 Set an offset from the current system time, in months, for the beginning of a certificate\*(Aqs validity period\&. Use when creating the certificate or adding it to a database\&. Express the offset in integers, using a minus sign (\-) to indicate a negative offset\&. If this argument is not used, the validity period begins at the current system time\&. The length of the validity period is set with the \-v argument\&. 606 .RE 607 .PP 608 \-X 609 .RS 4 610 Force the key and certificate database to open in read\-write mode\&. This is used with the 611 \fB\-U\fR 612 and 613 \fB\-L\fR 614 command options\&. 615 .RE 616 .PP 617 \-x 618 .RS 4 619 Use 620 \fBcertutil\fR 621 to generate the signature for a certificate being created or added to a database, rather than obtaining a signature from a separate CA\&. 622 .RE 623 .PP 624 \-y exp 625 .RS 4 626 Set an alternate exponent value to use in generating a new RSA public key for the database, instead of the default value of 65537\&. The available alternate values are 3 and 17\&. 627 .RE 628 .PP 629 \-\-pss 630 .RS 4 631 Restrict the generated certificate (with the 632 \fB\-S\fR 633 option) or certificate request (with the 634 \fB\-R\fR 635 option) to be used with the RSA\-PSS signature scheme\&. This only works when the private key of the certificate or certificate request is RSA\&. 636 .RE 637 .PP 638 \-\-pss\-sign 639 .RS 4 640 Sign the generated certificate with the RSA\-PSS signature scheme (with the 641 \fB\-C\fR 642 or 643 \fB\-S\fR 644 option)\&. This only works when the private key of the signer\*(Aqs certificate is RSA\&. If the signer\*(Aqs certificate is restricted to RSA\-PSS, it is not necessary to specify this option\&. 645 .RE 646 .PP 647 \-z noise\-file 648 .RS 4 649 Read a seed value from the specified file to generate a new private and public key pair\&. This argument makes it possible to use hardware\-generated seed values or manually create a value from the keyboard\&. The minimum file size is 20 bytes\&. 650 .RE 651 .PP 652 \-Z hashAlg 653 .RS 4 654 Specify the hash algorithm to use with the \-C, \-S or \-R command options\&. Possible keywords: 655 .sp 656 .RS 4 657 .ie n \{\ 658 \h'-04'\(bu\h'+03'\c 659 .\} 660 .el \{\ 661 .sp -1 662 .IP \(bu 2.3 663 .\} 664 MD2 665 .RE 666 .sp 667 .RS 4 668 .ie n \{\ 669 \h'-04'\(bu\h'+03'\c 670 .\} 671 .el \{\ 672 .sp -1 673 .IP \(bu 2.3 674 .\} 675 MD4 676 .RE 677 .sp 678 .RS 4 679 .ie n \{\ 680 \h'-04'\(bu\h'+03'\c 681 .\} 682 .el \{\ 683 .sp -1 684 .IP \(bu 2.3 685 .\} 686 MD5 687 .RE 688 .sp 689 .RS 4 690 .ie n \{\ 691 \h'-04'\(bu\h'+03'\c 692 .\} 693 .el \{\ 694 .sp -1 695 .IP \(bu 2.3 696 .\} 697 SHA1 698 .RE 699 .sp 700 .RS 4 701 .ie n \{\ 702 \h'-04'\(bu\h'+03'\c 703 .\} 704 .el \{\ 705 .sp -1 706 .IP \(bu 2.3 707 .\} 708 SHA224 709 .RE 710 .sp 711 .RS 4 712 .ie n \{\ 713 \h'-04'\(bu\h'+03'\c 714 .\} 715 .el \{\ 716 .sp -1 717 .IP \(bu 2.3 718 .\} 719 SHA256 720 .RE 721 .sp 722 .RS 4 723 .ie n \{\ 724 \h'-04'\(bu\h'+03'\c 725 .\} 726 .el \{\ 727 .sp -1 728 .IP \(bu 2.3 729 .\} 730 SHA384 731 .RE 732 .sp 733 .RS 4 734 .ie n \{\ 735 \h'-04'\(bu\h'+03'\c 736 .\} 737 .el \{\ 738 .sp -1 739 .IP \(bu 2.3 740 .\} 741 SHA512 742 .RE 743 .RE 744 .PP 745 \-0 SSO_password 746 .RS 4 747 Set a site security officer password on a token\&. 748 .RE 749 .PP 750 \-1 | \-\-keyUsage keyword,keyword 751 .RS 4 752 Set an X\&.509 V3 Certificate Type Extension in the certificate\&. There are several available keywords: 753 .sp 754 .RS 4 755 .ie n \{\ 756 \h'-04'\(bu\h'+03'\c 757 .\} 758 .el \{\ 759 .sp -1 760 .IP \(bu 2.3 761 .\} 762 digitalSignature 763 .RE 764 .sp 765 .RS 4 766 .ie n \{\ 767 \h'-04'\(bu\h'+03'\c 768 .\} 769 .el \{\ 770 .sp -1 771 .IP \(bu 2.3 772 .\} 773 nonRepudiation 774 .RE 775 .sp 776 .RS 4 777 .ie n \{\ 778 \h'-04'\(bu\h'+03'\c 779 .\} 780 .el \{\ 781 .sp -1 782 .IP \(bu 2.3 783 .\} 784 keyEncipherment 785 .RE 786 .sp 787 .RS 4 788 .ie n \{\ 789 \h'-04'\(bu\h'+03'\c 790 .\} 791 .el \{\ 792 .sp -1 793 .IP \(bu 2.3 794 .\} 795 dataEncipherment 796 .RE 797 .sp 798 .RS 4 799 .ie n \{\ 800 \h'-04'\(bu\h'+03'\c 801 .\} 802 .el \{\ 803 .sp -1 804 .IP \(bu 2.3 805 .\} 806 keyAgreement 807 .RE 808 .sp 809 .RS 4 810 .ie n \{\ 811 \h'-04'\(bu\h'+03'\c 812 .\} 813 .el \{\ 814 .sp -1 815 .IP \(bu 2.3 816 .\} 817 certSigning 818 .RE 819 .sp 820 .RS 4 821 .ie n \{\ 822 \h'-04'\(bu\h'+03'\c 823 .\} 824 .el \{\ 825 .sp -1 826 .IP \(bu 2.3 827 .\} 828 crlSigning 829 .RE 830 .sp 831 .RS 4 832 .ie n \{\ 833 \h'-04'\(bu\h'+03'\c 834 .\} 835 .el \{\ 836 .sp -1 837 .IP \(bu 2.3 838 .\} 839 critical 840 .RE 841 .RE 842 .PP 843 \-2 844 .RS 4 845 Add a basic constraint extension to a certificate that is being created or added to a database\&. This extension supports the certificate chain verification process\&. 846 \fBcertutil\fR 847 prompts for the certificate constraint extension to select\&. 848 .sp 849 X\&.509 certificate extensions are described in RFC 5280\&. 850 .RE 851 .PP 852 \-3 853 .RS 4 854 Add an authority key ID extension to a certificate that is being created or added to a database\&. This extension supports the identification of a particular certificate, from among multiple certificates associated with one subject name, as the correct issuer of a certificate\&. The Certificate Database Tool will prompt you to select the authority key ID extension\&. 855 .sp 856 X\&.509 certificate extensions are described in RFC 5280\&. 857 .RE 858 .PP 859 \-4 860 .RS 4 861 Add a CRL distribution point extension to a certificate that is being created or added to a database\&. This extension identifies the URL of a certificate\*(Aqs associated certificate revocation list (CRL)\&. 862 \fBcertutil\fR 863 prompts for the URL\&. 864 .sp 865 X\&.509 certificate extensions are described in RFC 5280\&. 866 .RE 867 .PP 868 \-5 | \-\-nsCertType keyword,keyword 869 .RS 4 870 Add an X\&.509 V3 certificate type extension to a certificate that is being created or added to the database\&. There are several available keywords: 871 .sp 872 .RS 4 873 .ie n \{\ 874 \h'-04'\(bu\h'+03'\c 875 .\} 876 .el \{\ 877 .sp -1 878 .IP \(bu 2.3 879 .\} 880 sslClient 881 .RE 882 .sp 883 .RS 4 884 .ie n \{\ 885 \h'-04'\(bu\h'+03'\c 886 .\} 887 .el \{\ 888 .sp -1 889 .IP \(bu 2.3 890 .\} 891 sslServer 892 .RE 893 .sp 894 .RS 4 895 .ie n \{\ 896 \h'-04'\(bu\h'+03'\c 897 .\} 898 .el \{\ 899 .sp -1 900 .IP \(bu 2.3 901 .\} 902 smime 903 .RE 904 .sp 905 .RS 4 906 .ie n \{\ 907 \h'-04'\(bu\h'+03'\c 908 .\} 909 .el \{\ 910 .sp -1 911 .IP \(bu 2.3 912 .\} 913 objectSigning 914 .RE 915 .sp 916 .RS 4 917 .ie n \{\ 918 \h'-04'\(bu\h'+03'\c 919 .\} 920 .el \{\ 921 .sp -1 922 .IP \(bu 2.3 923 .\} 924 sslCA 925 .RE 926 .sp 927 .RS 4 928 .ie n \{\ 929 \h'-04'\(bu\h'+03'\c 930 .\} 931 .el \{\ 932 .sp -1 933 .IP \(bu 2.3 934 .\} 935 smimeCA 936 .RE 937 .sp 938 .RS 4 939 .ie n \{\ 940 \h'-04'\(bu\h'+03'\c 941 .\} 942 .el \{\ 943 .sp -1 944 .IP \(bu 2.3 945 .\} 946 objectSigningCA 947 .RE 948 .sp 949 .RS 4 950 .ie n \{\ 951 \h'-04'\(bu\h'+03'\c 952 .\} 953 .el \{\ 954 .sp -1 955 .IP \(bu 2.3 956 .\} 957 critical 958 .RE 959 .sp 960 X\&.509 certificate extensions are described in RFC 5280\&. 961 .RE 962 .PP 963 \-6 | \-\-extKeyUsage keyword,keyword 964 .RS 4 965 Add an extended key usage extension to a certificate that is being created or added to the database\&. Several keywords are available: 966 .sp 967 .RS 4 968 .ie n \{\ 969 \h'-04'\(bu\h'+03'\c 970 .\} 971 .el \{\ 972 .sp -1 973 .IP \(bu 2.3 974 .\} 975 serverAuth 976 .RE 977 .sp 978 .RS 4 979 .ie n \{\ 980 \h'-04'\(bu\h'+03'\c 981 .\} 982 .el \{\ 983 .sp -1 984 .IP \(bu 2.3 985 .\} 986 clientAuth 987 .RE 988 .sp 989 .RS 4 990 .ie n \{\ 991 \h'-04'\(bu\h'+03'\c 992 .\} 993 .el \{\ 994 .sp -1 995 .IP \(bu 2.3 996 .\} 997 codeSigning 998 .RE 999 .sp 1000 .RS 4 1001 .ie n \{\ 1002 \h'-04'\(bu\h'+03'\c 1003 .\} 1004 .el \{\ 1005 .sp -1 1006 .IP \(bu 2.3 1007 .\} 1008 emailProtection 1009 .RE 1010 .sp 1011 .RS 4 1012 .ie n \{\ 1013 \h'-04'\(bu\h'+03'\c 1014 .\} 1015 .el \{\ 1016 .sp -1 1017 .IP \(bu 2.3 1018 .\} 1019 timeStamp 1020 .RE 1021 .sp 1022 .RS 4 1023 .ie n \{\ 1024 \h'-04'\(bu\h'+03'\c 1025 .\} 1026 .el \{\ 1027 .sp -1 1028 .IP \(bu 2.3 1029 .\} 1030 ocspResponder 1031 .RE 1032 .sp 1033 .RS 4 1034 .ie n \{\ 1035 \h'-04'\(bu\h'+03'\c 1036 .\} 1037 .el \{\ 1038 .sp -1 1039 .IP \(bu 2.3 1040 .\} 1041 stepUp 1042 .RE 1043 .sp 1044 .RS 4 1045 .ie n \{\ 1046 \h'-04'\(bu\h'+03'\c 1047 .\} 1048 .el \{\ 1049 .sp -1 1050 .IP \(bu 2.3 1051 .\} 1052 msTrustListSign 1053 .RE 1054 .sp 1055 .RS 4 1056 .ie n \{\ 1057 \h'-04'\(bu\h'+03'\c 1058 .\} 1059 .el \{\ 1060 .sp -1 1061 .IP \(bu 2.3 1062 .\} 1063 critical 1064 .RE 1065 .sp 1066 .RS 4 1067 .ie n \{\ 1068 \h'-04'\(bu\h'+03'\c 1069 .\} 1070 .el \{\ 1071 .sp -1 1072 .IP \(bu 2.3 1073 .\} 1074 x509Any 1075 .RE 1076 .sp 1077 .RS 4 1078 .ie n \{\ 1079 \h'-04'\(bu\h'+03'\c 1080 .\} 1081 .el \{\ 1082 .sp -1 1083 .IP \(bu 2.3 1084 .\} 1085 ipsecIKE 1086 .RE 1087 .sp 1088 .RS 4 1089 .ie n \{\ 1090 \h'-04'\(bu\h'+03'\c 1091 .\} 1092 .el \{\ 1093 .sp -1 1094 .IP \(bu 2.3 1095 .\} 1096 ipsecIKEEnd 1097 .RE 1098 .sp 1099 .RS 4 1100 .ie n \{\ 1101 \h'-04'\(bu\h'+03'\c 1102 .\} 1103 .el \{\ 1104 .sp -1 1105 .IP \(bu 2.3 1106 .\} 1107 ipsecIKEIntermediate 1108 .RE 1109 .sp 1110 .RS 4 1111 .ie n \{\ 1112 \h'-04'\(bu\h'+03'\c 1113 .\} 1114 .el \{\ 1115 .sp -1 1116 .IP \(bu 2.3 1117 .\} 1118 ipsecEnd 1119 .RE 1120 .sp 1121 .RS 4 1122 .ie n \{\ 1123 \h'-04'\(bu\h'+03'\c 1124 .\} 1125 .el \{\ 1126 .sp -1 1127 .IP \(bu 2.3 1128 .\} 1129 ipsecTunnel 1130 .RE 1131 .sp 1132 .RS 4 1133 .ie n \{\ 1134 \h'-04'\(bu\h'+03'\c 1135 .\} 1136 .el \{\ 1137 .sp -1 1138 .IP \(bu 2.3 1139 .\} 1140 ipsecUser 1141 .RE 1142 .sp 1143 X\&.509 certificate extensions are described in RFC 5280\&. 1144 .RE 1145 .PP 1146 \-7 emailAddrs 1147 .RS 4 1148 Add a comma\-separated list of email addresses to the subject alternative name extension of a certificate or certificate request that is being created or added to the database\&. Subject alternative name extensions are described in Section 4\&.2\&.1\&.7 of RFC 3280\&. 1149 .RE 1150 .PP 1151 \-8 dns\-names 1152 .RS 4 1153 Add a comma\-separated list of DNS names to the subject alternative name extension of a certificate or certificate request that is being created or added to the database\&. Subject alternative name extensions are described in Section 4\&.2\&.1\&.7 of RFC 3280\&. 1154 .RE 1155 .PP 1156 \-\-extAIA 1157 .RS 4 1158 Add the Authority Information Access extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1159 .RE 1160 .PP 1161 \-\-extSIA 1162 .RS 4 1163 Add the Subject Information Access extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1164 .RE 1165 .PP 1166 \-\-extCP 1167 .RS 4 1168 Add the Certificate Policies extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1169 .RE 1170 .PP 1171 \-\-extPM 1172 .RS 4 1173 Add the Policy Mappings extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1174 .RE 1175 .PP 1176 \-\-extPC 1177 .RS 4 1178 Add the Policy Constraints extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1179 .RE 1180 .PP 1181 \-\-extIA 1182 .RS 4 1183 Add the Inhibit Any Policy Access extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1184 .RE 1185 .PP 1186 \-\-extSKID 1187 .RS 4 1188 Add the Subject Key ID extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1189 .RE 1190 .PP 1191 \-\-extNC 1192 .RS 4 1193 Add a Name Constraint extension to the certificate\&. X\&.509 certificate extensions are described in RFC 5280\&. 1194 .RE 1195 .PP 1196 \-\-extSAN type:name[,type:name]\&.\&.\&. 1197 .RS 4 1198 Create a Subject Alt Name extension with one or multiple names\&. 1199 .sp 1200 \-type: directory, dn, dns, edi, ediparty, email, ip, ipaddr, other, registerid, rfc822, uri, x400, x400addr 1201 .RE 1202 .PP 1203 \-\-empty\-password 1204 .RS 4 1205 Use empty password when creating new certificate database with \-N\&. 1206 .RE 1207 .PP 1208 \-\-keyAttrFlags attrflags 1209 .RS 4 1210 PKCS #11 key Attributes\&. Comma separated list of key attribute flags, selected from the following list of choices: {token | session} {public | private} {sensitive | insensitive} {modifiable | unmodifiable} {extractable | unextractable} 1211 .RE 1212 .PP 1213 \-\-keyOpFlagsOn opflags, \-\-keyOpFlagsOff opflags 1214 .RS 4 1215 PKCS #11 key Operation Flags\&. Comma separated list of one or more of the following: {token | session} {public | private} {sensitive | insensitive} {modifiable | unmodifiable} {extractable | unextractable} 1216 .RE 1217 .PP 1218 \-\-new\-n nickname 1219 .RS 4 1220 A new nickname, used when renaming a certificate\&. 1221 .RE 1222 .PP 1223 \-\-source\-dir certdir 1224 .RS 4 1225 Identify the certificate database directory to upgrade\&. 1226 .RE 1227 .PP 1228 \-\-source\-prefix certdir 1229 .RS 4 1230 Give the prefix of the certificate and key databases to upgrade\&. 1231 .RE 1232 .PP 1233 \-\-upgrade\-id uniqueID 1234 .RS 4 1235 Give the unique ID of the database to upgrade\&. 1236 .RE 1237 .PP 1238 \-\-upgrade\-token\-name name 1239 .RS 4 1240 Set the name of the token to use while it is being upgraded\&. 1241 .RE 1242 .PP 1243 \-@ pwfile 1244 .RS 4 1245 Give the name of a password file to use for the database being upgraded\&. 1246 .RE 1247 .SH "USAGE AND EXAMPLES" 1248 .PP 1249 Most of the command options in the examples listed here have more arguments available\&. The arguments included in these examples are the most common ones or are used to illustrate a specific scenario\&. Use the 1250 \fB\-H\fR 1251 option to show the complete list of arguments for each command option\&. 1252 .PP 1253 \fBCreating New Security Databases\fR 1254 .PP 1255 Certificates, keys, and security modules related to managing certificates are stored in three related databases: 1256 .sp 1257 .RS 4 1258 .ie n \{\ 1259 \h'-04'\(bu\h'+03'\c 1260 .\} 1261 .el \{\ 1262 .sp -1 1263 .IP \(bu 2.3 1264 .\} 1265 cert8\&.db or cert9\&.db 1266 .RE 1267 .sp 1268 .RS 4 1269 .ie n \{\ 1270 \h'-04'\(bu\h'+03'\c 1271 .\} 1272 .el \{\ 1273 .sp -1 1274 .IP \(bu 2.3 1275 .\} 1276 key3\&.db or key4\&.db 1277 .RE 1278 .sp 1279 .RS 4 1280 .ie n \{\ 1281 \h'-04'\(bu\h'+03'\c 1282 .\} 1283 .el \{\ 1284 .sp -1 1285 .IP \(bu 2.3 1286 .\} 1287 secmod\&.db or pkcs11\&.txt 1288 .RE 1289 .PP 1290 These databases must be created before certificates or keys can be generated\&. 1291 .sp 1292 .if n \{\ 1293 .RS 4 1294 .\} 1295 .nf 1296 certutil \-N \-d directory 1297 .fi 1298 .if n \{\ 1299 .RE 1300 .\} 1301 .PP 1302 \fBCreating a Certificate Request\fR 1303 .PP 1304 A certificate request contains most or all of the information that is used to generate the final certificate\&. This request is submitted separately to a certificate authority and is then approved by some mechanism (automatically or by human review)\&. Once the request is approved, then the certificate is generated\&. 1305 .sp 1306 .if n \{\ 1307 .RS 4 1308 .\} 1309 .nf 1310 $ 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] 1311 .fi 1312 .if n \{\ 1313 .RE 1314 .\} 1315 .PP 1316 The 1317 \fB\-R\fR 1318 command options requires four arguments: 1319 .sp 1320 .RS 4 1321 .ie n \{\ 1322 \h'-04'\(bu\h'+03'\c 1323 .\} 1324 .el \{\ 1325 .sp -1 1326 .IP \(bu 2.3 1327 .\} 1328 \fB\-k\fR 1329 to specify either the key type to generate or, when renewing a certificate, the existing key pair to use 1330 .RE 1331 .sp 1332 .RS 4 1333 .ie n \{\ 1334 \h'-04'\(bu\h'+03'\c 1335 .\} 1336 .el \{\ 1337 .sp -1 1338 .IP \(bu 2.3 1339 .\} 1340 \fB\-g\fR 1341 to set the keysize of the key to generate 1342 .RE 1343 .sp 1344 .RS 4 1345 .ie n \{\ 1346 \h'-04'\(bu\h'+03'\c 1347 .\} 1348 .el \{\ 1349 .sp -1 1350 .IP \(bu 2.3 1351 .\} 1352 \fB\-s\fR 1353 to set the subject name of the certificate 1354 .RE 1355 .sp 1356 .RS 4 1357 .ie n \{\ 1358 \h'-04'\(bu\h'+03'\c 1359 .\} 1360 .el \{\ 1361 .sp -1 1362 .IP \(bu 2.3 1363 .\} 1364 \fB\-d\fR 1365 to give the security database directory 1366 .RE 1367 .PP 1368 The new certificate request can be output in ASCII format (\fB\-a\fR) or can be written to a specified file (\fB\-o\fR)\&. 1369 .PP 1370 For example: 1371 .sp 1372 .if n \{\ 1373 .RS 4 1374 .\} 1375 .nf 1376 $ 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 1377 1378 Generating key\&. This may take a few moments\&.\&.\&. 1379 1380 .fi 1381 .if n \{\ 1382 .RE 1383 .\} 1384 .PP 1385 \fBCreating a Certificate\fR 1386 .PP 1387 A valid certificate must be issued by a trusted CA\&. This can be done by specifying a CA certificate (\fB\-c\fR) that is stored in the certificate database\&. If a CA key pair is not available, you can create a self\-signed certificate using the 1388 \fB\-x\fR 1389 argument with the 1390 \fB\-S\fR 1391 command option\&. 1392 .sp 1393 .if n \{\ 1394 .RS 4 1395 .\} 1396 .nf 1397 $ 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] 1398 .fi 1399 .if n \{\ 1400 .RE 1401 .\} 1402 .PP 1403 The series of numbers and 1404 \fB\-\-ext*\fR 1405 options set certificate extensions that can be added to the certificate when it is generated by the CA\&. Interactive prompts will result\&. 1406 .PP 1407 For example, this creates a self\-signed certificate: 1408 .sp 1409 .if n \{\ 1410 .RS 4 1411 .\} 1412 .nf 1413 $ certutil \-S \-s "CN=Example CA" \-n my\-ca\-cert \-x \-t "C,C,C" \-1 \-2 \-5 \-m 3650 1414 .fi 1415 .if n \{\ 1416 .RE 1417 .\} 1418 .PP 1419 The interative prompts for key usage and whether any extensions are critical and responses have been ommitted for brevity\&. 1420 .PP 1421 From there, new certificates can reference the self\-signed certificate: 1422 .sp 1423 .if n \{\ 1424 .RS 4 1425 .\} 1426 .nf 1427 $ certutil \-S \-s "CN=My Server Cert" \-n my\-server\-cert \-c "my\-ca\-cert" \-t ",," \-1 \-5 \-6 \-8 \-m 730 1428 .fi 1429 .if n \{\ 1430 .RE 1431 .\} 1432 .PP 1433 \fBGenerating a Certificate from a Certificate Request\fR 1434 .PP 1435 When a certificate request is created, a certificate can be generated by using the request and then referencing a certificate authority signing certificate (the 1436 \fIissuer\fR 1437 specified in the 1438 \fB\-c\fR 1439 argument)\&. The issuing certificate must be in the certificate database in the specified directory\&. 1440 .sp 1441 .if n \{\ 1442 .RS 4 1443 .\} 1444 .nf 1445 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] 1446 .fi 1447 .if n \{\ 1448 .RE 1449 .\} 1450 .PP 1451 For example: 1452 .sp 1453 .if n \{\ 1454 .RS 4 1455 .\} 1456 .nf 1457 $ 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 1458 .fi 1459 .if n \{\ 1460 .RE 1461 .\} 1462 .PP 1463 \fBListing Certificates\fR 1464 .PP 1465 The 1466 \fB\-L\fR 1467 command option lists all of the certificates listed in the certificate database\&. The path to the directory (\fB\-d\fR) is required\&. 1468 .sp 1469 .if n \{\ 1470 .RS 4 1471 .\} 1472 .nf 1473 $ certutil \-L \-d /home/my/sharednssdb 1474 1475 Certificate Nickname Trust Attributes 1476 SSL,S/MIME,JAR/XPI 1477 1478 CA Administrator of Instance pki\-ca1\*(Aqs Example Domain ID u,u,u 1479 TPS Administrator\*(Aqs Example Domain ID u,u,u 1480 Google Internet Authority ,, 1481 Certificate Authority \- Example Domain CT,C,C 1482 .fi 1483 .if n \{\ 1484 .RE 1485 .\} 1486 .PP 1487 Using additional arguments with 1488 \fB\-L\fR 1489 can return and print the information for a single, specific certificate\&. For example, the 1490 \fB\-n\fR 1491 argument passes the certificate name, while the 1492 \fB\-a\fR 1493 argument prints the certificate in ASCII format: 1494 .sp 1495 .if n \{\ 1496 .RS 4 1497 .\} 1498 .nf 1499 $ certutil \-L \-d $HOME/nssdb \-a \-n my\-ca\-cert 1500 \-\-\-\-\-BEGIN CERTIFICATE\-\-\-\-\- 1501 MIIB1DCCAT2gAwIBAgICDkIwDQYJKoZIhvcNAQEFBQAwFTETMBEGA1UEAxMKRXhh 1502 bXBsZSBDQTAeFw0xMzAzMTMxOTEwMjlaFw0xMzA2MTMxOTEwMjlaMBUxEzARBgNV 1503 BAMTCkV4YW1wbGUgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJ4Kzqvz 1504 JyBVgFqDXRYSyTBNw1DrxUU/3GvWA/ngjAwHEv0Cul/6sO/gsCvnABHiH6unns6x 1505 XRzPORlC2WY3gkk7vmlsLvYpyecNazAi/NAwVnU/66HOsaoVFWE+gBQo99UrN2yk 1506 0BiK/GMFlLm5dXQROgA9ZKKyFdI0LIXtf6SbAgMBAAGjMzAxMBEGCWCGSAGG+EIB 1507 AQQEAwIHADAMBgNVHRMEBTADAQH/MA4GA1UdDwEB/wQEAwICBDANBgkqhkiG9w0B 1508 AQUFAAOBgQA6chkzkACN281d1jKMrc+RHG2UMaQyxiteaLVZO+Ro1nnRUvseDf09 1509 XKYFwPMJjWCihVku6bw/ihZfuMHhxK22Nue6inNQ6eDu7WmrqL8z3iUrQwxs+WiF 1510 ob2rb8XRVVJkzXdXxlk4uo3UtNvw8sAz7sWD71qxKaIHU5q49zijfg== 1511 \-\-\-\-\-END CERTIFICATE\-\-\-\-\- 1512 .fi 1513 .if n \{\ 1514 .RE 1515 .\} 1516 .PP 1517 For a human\-readable display 1518 .sp 1519 .if n \{\ 1520 .RS 4 1521 .\} 1522 .nf 1523 $ certutil \-L \-d $HOME/nssdb \-n my\-ca\-cert 1524 Certificate: 1525 Data: 1526 Version: 3 (0x2) 1527 Serial Number: 3650 (0xe42) 1528 Signature Algorithm: PKCS #1 SHA\-1 With RSA Encryption 1529 Issuer: "CN=Example CA" 1530 Validity: 1531 Not Before: Wed Mar 13 19:10:29 2013 1532 Not After : Thu Jun 13 19:10:29 2013 1533 Subject: "CN=Example CA" 1534 Subject Public Key Info: 1535 Public Key Algorithm: PKCS #1 RSA Encryption 1536 RSA Public Key: 1537 Modulus: 1538 9e:0a:ce:ab:f3:27:20:55:80:5a:83:5d:16:12:c9:30: 1539 4d:c3:50:eb:c5:45:3f:dc:6b:d6:03:f9:e0:8c:0c:07: 1540 12:fd:02:ba:5f:fa:b0:ef:e0:b0:2b:e7:00:11:e2:1f: 1541 ab:a7:9e:ce:b1:5d:1c:cf:39:19:42:d9:66:37:82:49: 1542 3b:be:69:6c:2e:f6:29:c9:e7:0d:6b:30:22:fc:d0:30: 1543 56:75:3f:eb:a1:ce:b1:aa:15:15:61:3e:80:14:28:f7: 1544 d5:2b:37:6c:a4:d0:18:8a:fc:63:05:94:b9:b9:75:74: 1545 11:3a:00:3d:64:a2:b2:15:d2:34:2c:85:ed:7f:a4:9b 1546 Exponent: 65537 (0x10001) 1547 Signed Extensions: 1548 Name: Certificate Type 1549 Data: none 1550 1551 Name: Certificate Basic Constraints 1552 Data: Is a CA with no maximum path length\&. 1553 1554 Name: Certificate Key Usage 1555 Critical: True 1556 Usages: Certificate Signing 1557 1558 Signature Algorithm: PKCS #1 SHA\-1 With RSA Encryption 1559 Signature: 1560 3a:72:19:33:90:00:8d:db:cd:5d:d6:32:8c:ad:cf:91: 1561 1c:6d:94:31:a4:32:c6:2b:5e:68:b5:59:3b:e4:68:d6: 1562 79:d1:52:fb:1e:0d:fd:3d:5c:a6:05:c0:f3:09:8d:60: 1563 a2:85:59:2e:e9:bc:3f:8a:16:5f:b8:c1:e1:c4:ad:b6: 1564 36:e7:ba:8a:73:50:e9:e0:ee:ed:69:ab:a8:bf:33:de: 1565 25:2b:43:0c:6c:f9:68:85:a1:bd:ab:6f:c5:d1:55:52: 1566 64:cd:77:57:c6:59:38:ba:8d:d4:b4:db:f0:f2:c0:33: 1567 ee:c5:83:ef:5a:b1:29:a2:07:53:9a:b8:f7:38:a3:7e 1568 Fingerprint (MD5): 1569 86:D8:A5:8B:8A:26:BE:9E:17:A8:7B:66:10:6B:27:80 1570 Fingerprint (SHA1): 1571 48:78:09:EF:C5:D4:0C:BD:D2:64:45:59:EB:03:13:15:F7:A9:D6:F7 1572 1573 Certificate Trust Flags: 1574 SSL Flags: 1575 Valid CA 1576 Trusted CA 1577 User 1578 Email Flags: 1579 Valid CA 1580 Trusted CA 1581 User 1582 Object Signing Flags: 1583 Valid CA 1584 Trusted CA 1585 User 1586 1587 .fi 1588 .if n \{\ 1589 .RE 1590 .\} 1591 .PP 1592 \fBListing Keys\fR 1593 .PP 1594 Keys are the original material used to encrypt certificate data\&. The keys generated for certificates are stored separately, in the key database\&. 1595 .PP 1596 To list all keys in the database, use the 1597 \fB\-K\fR 1598 command option and the (required) 1599 \fB\-d\fR 1600 argument to give the path to the directory\&. 1601 .sp 1602 .if n \{\ 1603 .RS 4 1604 .\} 1605 .nf 1606 $ certutil \-K \-d $HOME/nssdb 1607 certutil: Checking token "NSS Certificate DB" in slot "NSS User Private Key and Certificate Services " 1608 < 0> rsa 455a6673bde9375c2887ec8bf8016b3f9f35861d Thawte Freemail Member\*(Aqs Thawte Consulting (Pty) Ltd\&. ID 1609 < 1> rsa 40defeeb522ade11090eacebaaf1196a172127df Example Domain Administrator Cert 1610 < 2> rsa 1d0b06f44f6c03842f7d4f4a1dc78b3bcd1b85a5 John Smith user cert 1611 .fi 1612 .if n \{\ 1613 .RE 1614 .\} 1615 .PP 1616 There are ways to narrow the keys listed in the search results: 1617 .sp 1618 .RS 4 1619 .ie n \{\ 1620 \h'-04'\(bu\h'+03'\c 1621 .\} 1622 .el \{\ 1623 .sp -1 1624 .IP \(bu 2.3 1625 .\} 1626 To return a specific key, use the 1627 \fB\-n\fR 1628 \fIname\fR 1629 argument with the name of the key\&. 1630 .RE 1631 .sp 1632 .RS 4 1633 .ie n \{\ 1634 \h'-04'\(bu\h'+03'\c 1635 .\} 1636 .el \{\ 1637 .sp -1 1638 .IP \(bu 2.3 1639 .\} 1640 If there are multiple security devices loaded, then the 1641 \fB\-h\fR 1642 \fItokenname\fR 1643 argument can search a specific token or all tokens\&. 1644 .RE 1645 .sp 1646 .RS 4 1647 .ie n \{\ 1648 \h'-04'\(bu\h'+03'\c 1649 .\} 1650 .el \{\ 1651 .sp -1 1652 .IP \(bu 2.3 1653 .\} 1654 If there are multiple key types available, then the 1655 \fB\-k\fR 1656 \fIkey\-type\fR 1657 argument can search a specific type of key, like RSA, DSA, or ECC\&. 1658 .RE 1659 .PP 1660 \fBListing Security Modules\fR 1661 .PP 1662 The devices that can be used to store certificates \-\- both internal databases and external devices like smart cards \-\- are recognized and used by loading security modules\&. The 1663 \fB\-U\fR 1664 command option lists all of the security modules listed in the 1665 secmod\&.db 1666 database\&. The path to the directory (\fB\-d\fR) is required\&. 1667 .sp 1668 .if n \{\ 1669 .RS 4 1670 .\} 1671 .nf 1672 $ certutil \-U \-d /home/my/sharednssdb 1673 1674 slot: NSS User Private Key and Certificate Services 1675 token: NSS Certificate DB 1676 uri: pkcs11:token=NSS%20Certificate%20DB;manufacturer=Mozilla%20Foundation;serial=0000000000000000;model=NSS%203 1677 1678 slot: NSS Internal Cryptographic Services 1679 token: NSS Generic Crypto Services 1680 uri: pkcs11:token=NSS%20Generic%20Crypto%20Services;manufacturer=Mozilla%20Foundation;serial=0000000000000000;model=NSS%203 1681 .fi 1682 .if n \{\ 1683 .RE 1684 .\} 1685 .PP 1686 \fBAdding Certificates to the Database\fR 1687 .PP 1688 Existing certificates or certificate requests can be added manually to the certificate database, even if they were generated elsewhere\&. This uses the 1689 \fB\-A\fR 1690 command option\&. 1691 .sp 1692 .if n \{\ 1693 .RS 4 1694 .\} 1695 .nf 1696 certutil \-A \-n certname \-t trustargs \-d directory [\-a] [\-i input\-file] 1697 .fi 1698 .if n \{\ 1699 .RE 1700 .\} 1701 .PP 1702 For example: 1703 .sp 1704 .if n \{\ 1705 .RS 4 1706 .\} 1707 .nf 1708 $ certutil \-A \-n "CN=My SSL Certificate" \-t ",," \-d /home/my/sharednssdb \-i /home/example\-certs/cert\&.cer 1709 .fi 1710 .if n \{\ 1711 .RE 1712 .\} 1713 .PP 1714 A related command option, 1715 \fB\-E\fR, is used specifically to add email certificates to the certificate database\&. The 1716 \fB\-E\fR 1717 command has the same arguments as the 1718 \fB\-A\fR 1719 command\&. The trust arguments for certificates have the format 1720 \fISSL,S/MIME,Code\-signing\fR, so the middle trust settings relate most to email certificates (though the others can be set)\&. For example: 1721 .sp 1722 .if n \{\ 1723 .RS 4 1724 .\} 1725 .nf 1726 $ certutil \-E \-n "CN=John Smith Email Cert" \-t ",P," \-d /home/my/sharednssdb \-i /home/example\-certs/email\&.cer 1727 .fi 1728 .if n \{\ 1729 .RE 1730 .\} 1731 .PP 1732 \fBDeleting Certificates to the Database\fR 1733 .PP 1734 Certificates can be deleted from a database using the 1735 \fB\-D\fR 1736 option\&. The only required options are to give the security database directory and to identify the certificate nickname\&. 1737 .sp 1738 .if n \{\ 1739 .RS 4 1740 .\} 1741 .nf 1742 certutil \-D \-d directory \-n "nickname" 1743 .fi 1744 .if n \{\ 1745 .RE 1746 .\} 1747 .PP 1748 For example: 1749 .sp 1750 .if n \{\ 1751 .RS 4 1752 .\} 1753 .nf 1754 $ certutil \-D \-d /home/my/sharednssdb \-n "my\-ssl\-cert" 1755 .fi 1756 .if n \{\ 1757 .RE 1758 .\} 1759 .PP 1760 \fBValidating Certificates\fR 1761 .PP 1762 A certificate contains an expiration date in itself, and expired certificates are easily rejected\&. However, certificates can also be revoked before they hit their expiration date\&. Checking whether a certificate has been revoked requires validating the certificate\&. Validation can also be used to ensure that the certificate is only used for the purposes it was initially issued for\&. Validation is carried out by the 1763 \fB\-V\fR 1764 command option\&. 1765 .sp 1766 .if n \{\ 1767 .RS 4 1768 .\} 1769 .nf 1770 certutil \-V \-n certificate\-name [\-b time] [\-e] [\-u cert\-usage] \-d directory 1771 .fi 1772 .if n \{\ 1773 .RE 1774 .\} 1775 .PP 1776 For example, to validate an email certificate: 1777 .sp 1778 .if n \{\ 1779 .RS 4 1780 .\} 1781 .nf 1782 $ certutil \-V \-n "John Smith\*(Aqs Email Cert" \-e \-u S,R \-d /home/my/sharednssdb 1783 .fi 1784 .if n \{\ 1785 .RE 1786 .\} 1787 .PP 1788 \fBModifying Certificate Trust Settings\fR 1789 .PP 1790 The trust settings (which relate to the operations that a certificate is allowed to be used for) can be changed after a certificate is created or added to the database\&. This is especially useful for CA certificates, but it can be performed for any type of certificate\&. 1791 .sp 1792 .if n \{\ 1793 .RS 4 1794 .\} 1795 .nf 1796 certutil \-M \-n certificate\-name \-t trust\-args \-d directory 1797 .fi 1798 .if n \{\ 1799 .RE 1800 .\} 1801 .PP 1802 For example: 1803 .sp 1804 .if n \{\ 1805 .RS 4 1806 .\} 1807 .nf 1808 $ certutil \-M \-n "My CA Certificate" \-d /home/my/sharednssdb \-t "CT,CT,CT" 1809 .fi 1810 .if n \{\ 1811 .RE 1812 .\} 1813 .PP 1814 \fBPrinting the Certificate Chain\fR 1815 .PP 1816 Certificates can be issued in 1817 \fIchains\fR 1818 because every certificate authority itself has a certificate; when a CA issues a certificate, it essentially stamps that certificate with its own fingerprint\&. The 1819 \fB\-O\fR 1820 prints the full chain of a certificate, going from the initial CA (the root CA) through ever intermediary CA to the actual certificate\&. For example, for an email certificate with two CAs in the chain: 1821 .sp 1822 .if n \{\ 1823 .RS 4 1824 .\} 1825 .nf 1826 $ certutil \-d /home/my/sharednssdb \-O \-n "jsmith@example\&.com" 1827 "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] 1828 1829 "Thawte Personal Freemail Issuing CA \- Thawte Consulting" [CN=Thawte Personal Freemail Issuing CA,O=Thawte Consulting (Pty) Ltd\&.,C=ZA] 1830 1831 "(null)" [E=jsmith@example\&.com,CN=Thawte Freemail Member] 1832 .fi 1833 .if n \{\ 1834 .RE 1835 .\} 1836 .PP 1837 \fBResetting a Token\fR 1838 .PP 1839 The device which stores certificates \-\- both external hardware devices and internal software databases \-\- can be blanked and reused\&. This operation is performed on the device which stores the data, not directly on the security databases, so the location must be referenced through the token name (\fB\-h\fR) as well as any directory path\&. If there is no external token used, the default value is internal\&. 1840 .sp 1841 .if n \{\ 1842 .RS 4 1843 .\} 1844 .nf 1845 certutil \-T \-d directory \-h token\-name \-0 security\-officer\-password 1846 .fi 1847 .if n \{\ 1848 .RE 1849 .\} 1850 .PP 1851 Many networks have dedicated personnel who handle changes to security tokens (the security officer)\&. This person must supply the password to access the specified token\&. For example: 1852 .sp 1853 .if n \{\ 1854 .RS 4 1855 .\} 1856 .nf 1857 $ certutil \-T \-d /home/my/sharednssdb \-h nethsm \-0 secret 1858 .fi 1859 .if n \{\ 1860 .RE 1861 .\} 1862 .PP 1863 \fBUpgrading or Merging the Security Databases\fR 1864 .PP 1865 Many networks or applications may be using older BerkeleyDB versions of the certificate database (cert8\&.db)\&. Databases can be upgraded to the new SQLite version of the database (cert9\&.db) using the 1866 \fB\-\-upgrade\-merge\fR 1867 command option or existing databases can be merged with the new 1868 cert9\&.db 1869 databases using the 1870 \fB\-\-\-merge\fR 1871 command\&. 1872 .PP 1873 The 1874 \fB\-\-upgrade\-merge\fR 1875 command must give information about the original database and then use the standard arguments (like 1876 \fB\-d\fR) to give the information about the new databases\&. The command also requires information that the tool uses for the process to upgrade and write over the original database\&. 1877 .sp 1878 .if n \{\ 1879 .RS 4 1880 .\} 1881 .nf 1882 certutil \-\-upgrade\-merge \-d directory [\-P dbprefix] \-\-source\-dir directory \-\-source\-prefix dbprefix \-\-upgrade\-id id \-\-upgrade\-token\-name name [\-@ password\-file] 1883 .fi 1884 .if n \{\ 1885 .RE 1886 .\} 1887 .PP 1888 For example: 1889 .sp 1890 .if n \{\ 1891 .RS 4 1892 .\} 1893 .nf 1894 $ certutil \-\-upgrade\-merge \-d /home/my/sharednssdb \-\-source\-dir /opt/my\-app/alias/ \-\-source\-prefix serverapp\- \-\-upgrade\-id 1 \-\-upgrade\-token\-name internal 1895 .fi 1896 .if n \{\ 1897 .RE 1898 .\} 1899 .PP 1900 The 1901 \fB\-\-merge\fR 1902 command only requires information about the location of the original database; since it doesn\*(Aqt change the format of the database, it can write over information without performing interim step\&. 1903 .sp 1904 .if n \{\ 1905 .RS 4 1906 .\} 1907 .nf 1908 certutil \-\-merge \-d directory [\-P dbprefix] \-\-source\-dir directory \-\-source\-prefix dbprefix [\-@ password\-file] 1909 .fi 1910 .if n \{\ 1911 .RE 1912 .\} 1913 .PP 1914 For example: 1915 .sp 1916 .if n \{\ 1917 .RS 4 1918 .\} 1919 .nf 1920 $ certutil \-\-merge \-d /home/my/sharednssdb \-\-source\-dir /opt/my\-app/alias/ \-\-source\-prefix serverapp\- 1921 .fi 1922 .if n \{\ 1923 .RE 1924 .\} 1925 .PP 1926 \fBRunning certutil Commands from a Batch File\fR 1927 .PP 1928 A series of commands can be run sequentially from a text file with the 1929 \fB\-B\fR 1930 command option\&. The only argument for this specifies the input file\&. 1931 .sp 1932 .if n \{\ 1933 .RS 4 1934 .\} 1935 .nf 1936 $ certutil \-B \-i /path/to/batch\-file 1937 .fi 1938 .if n \{\ 1939 .RE 1940 .\} 1941 .SH "NSS DATABASE TYPES" 1942 .PP 1943 NSS originally used BerkeleyDB databases to store security information\&. The last versions of these 1944 \fIlegacy\fR 1945 databases are: 1946 .sp 1947 .RS 4 1948 .ie n \{\ 1949 \h'-04'\(bu\h'+03'\c 1950 .\} 1951 .el \{\ 1952 .sp -1 1953 .IP \(bu 2.3 1954 .\} 1955 cert8\&.db for certificates 1956 .RE 1957 .sp 1958 .RS 4 1959 .ie n \{\ 1960 \h'-04'\(bu\h'+03'\c 1961 .\} 1962 .el \{\ 1963 .sp -1 1964 .IP \(bu 2.3 1965 .\} 1966 key3\&.db for keys 1967 .RE 1968 .sp 1969 .RS 4 1970 .ie n \{\ 1971 \h'-04'\(bu\h'+03'\c 1972 .\} 1973 .el \{\ 1974 .sp -1 1975 .IP \(bu 2.3 1976 .\} 1977 secmod\&.db for PKCS #11 module information 1978 .RE 1979 .PP 1980 BerkeleyDB has performance limitations, though, which prevent it from being easily used by multiple applications simultaneously\&. NSS has some flexibility that allows applications to use their own, independent database engine while keeping a shared database and working around the access issues\&. Still, NSS requires more flexibility to provide a truly shared security database\&. 1981 .PP 1982 In 2009, NSS introduced a new set of databases that are SQLite databases rather than BerkeleyDB\&. These new databases provide more accessibility and performance: 1983 .sp 1984 .RS 4 1985 .ie n \{\ 1986 \h'-04'\(bu\h'+03'\c 1987 .\} 1988 .el \{\ 1989 .sp -1 1990 .IP \(bu 2.3 1991 .\} 1992 cert9\&.db for certificates 1993 .RE 1994 .sp 1995 .RS 4 1996 .ie n \{\ 1997 \h'-04'\(bu\h'+03'\c 1998 .\} 1999 .el \{\ 2000 .sp -1 2001 .IP \(bu 2.3 2002 .\} 2003 key4\&.db for keys 2004 .RE 2005 .sp 2006 .RS 4 2007 .ie n \{\ 2008 \h'-04'\(bu\h'+03'\c 2009 .\} 2010 .el \{\ 2011 .sp -1 2012 .IP \(bu 2.3 2013 .\} 2014 pkcs11\&.txt, a listing of all of the PKCS #11 modules, contained in a new subdirectory in the security databases directory 2015 .RE 2016 .PP 2017 Because the SQLite databases are designed to be shared, these are the 2018 \fIshared\fR 2019 database type\&. The shared database type is preferred; the legacy format is included for backward compatibility\&. 2020 .PP 2021 By default, the tools (\fBcertutil\fR, 2022 \fBpk12util\fR, 2023 \fBmodutil\fR) assume that the given security databases use the SQLite type\&. Using the legacy databases must be manually specified by using the 2024 \fBdbm:\fR 2025 prefix with the given security directory\&. For example: 2026 .sp 2027 .if n \{\ 2028 .RS 4 2029 .\} 2030 .nf 2031 $ certutil \-L \-d dbm:/home/my/sharednssdb 2032 .fi 2033 .if n \{\ 2034 .RE 2035 .\} 2036 .PP 2037 To set the legacy database type as the default type for the tools, set the 2038 \fBNSS_DEFAULT_DB_TYPE\fR 2039 environment variable to 2040 \fBdbm\fR: 2041 .sp 2042 .if n \{\ 2043 .RS 4 2044 .\} 2045 .nf 2046 export NSS_DEFAULT_DB_TYPE="dbm" 2047 .fi 2048 .if n \{\ 2049 .RE 2050 .\} 2051 .PP 2052 This line can be set added to the 2053 ~/\&.bashrc 2054 file to make the change permanent\&. 2055 .sp 2056 .RS 4 2057 .ie n \{\ 2058 \h'-04'\(bu\h'+03'\c 2059 .\} 2060 .el \{\ 2061 .sp -1 2062 .IP \(bu 2.3 2063 .\} 2064 https://wiki\&.mozilla\&.org/NSS_Shared_DB_Howto 2065 .RE 2066 .PP 2067 For an engineering draft on the changes in the shared NSS databases, see the NSS project wiki: 2068 .sp 2069 .RS 4 2070 .ie n \{\ 2071 \h'-04'\(bu\h'+03'\c 2072 .\} 2073 .el \{\ 2074 .sp -1 2075 .IP \(bu 2.3 2076 .\} 2077 https://wiki\&.mozilla\&.org/NSS_Shared_DB 2078 .RE 2079 .SH "SEE ALSO" 2080 .PP 2081 pk12util (1) 2082 .PP 2083 modutil (1) 2084 .PP 2085 \fBcertutil\fR 2086 has arguments or operations that use features defined in several IETF RFCs\&. 2087 .sp 2088 .RS 4 2089 .ie n \{\ 2090 \h'-04'\(bu\h'+03'\c 2091 .\} 2092 .el \{\ 2093 .sp -1 2094 .IP \(bu 2.3 2095 .\} 2096 http://tools\&.ietf\&.org/html/rfc5280 2097 .RE 2098 .sp 2099 .RS 4 2100 .ie n \{\ 2101 \h'-04'\(bu\h'+03'\c 2102 .\} 2103 .el \{\ 2104 .sp -1 2105 .IP \(bu 2.3 2106 .\} 2107 http://tools\&.ietf\&.org/html/rfc1113 2108 .RE 2109 .sp 2110 .RS 4 2111 .ie n \{\ 2112 \h'-04'\(bu\h'+03'\c 2113 .\} 2114 .el \{\ 2115 .sp -1 2116 .IP \(bu 2.3 2117 .\} 2118 http://tools\&.ietf\&.org/html/rfc1485 2119 .RE 2120 .PP 2121 The NSS wiki has information on the new database design and how to configure applications to use it\&. 2122 .sp 2123 .RS 4 2124 .ie n \{\ 2125 \h'-04'\(bu\h'+03'\c 2126 .\} 2127 .el \{\ 2128 .sp -1 2129 .IP \(bu 2.3 2130 .\} 2131 https://wiki\&.mozilla\&.org/NSS_Shared_DB_Howto 2132 .RE 2133 .sp 2134 .RS 4 2135 .ie n \{\ 2136 \h'-04'\(bu\h'+03'\c 2137 .\} 2138 .el \{\ 2139 .sp -1 2140 .IP \(bu 2.3 2141 .\} 2142 https://wiki\&.mozilla\&.org/NSS_Shared_DB 2143 .RE 2144 .SH "ADDITIONAL RESOURCES" 2145 .PP 2146 For information about NSS and other tools related to NSS (like JSS), check out the NSS project wiki at 2147 \m[blue]\fBhttp://www\&.mozilla\&.org/projects/security/pki/nss/\fR\m[]\&. The NSS site relates directly to NSS code changes and releases\&. 2148 .PP 2149 Mailing lists: https://lists\&.mozilla\&.org/listinfo/dev\-tech\-crypto 2150 .PP 2151 IRC: Freenode at #dogtag\-pki 2152 .SH "AUTHORS" 2153 .PP 2154 The NSS tools were written and maintained by developers with Netscape, Red Hat, Sun, Oracle, Mozilla, and Google\&. 2155 .PP 2156 Authors: Elio Maldonado <emaldona@redhat\&.com>, Deon Lackey <dlackey@redhat\&.com>\&. 2157 .SH "LICENSE" 2158 .PP 2159 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/\&. 2160 .SH "NOTES" 2161 .IP " 1." 4 2162 Mozilla NSS bug 836477 2163 .RS 4 2164 \%https://bugzilla.mozilla.org/show_bug.cgi?id=836477 2165 .RE