lh | 9ed821d | 2023-04-07 01:36:19 -0700 | [diff] [blame] | 1 | =pod |
| 2 | |
| 3 | =head1 NAME |
| 4 | |
| 5 | openssl-nseq, |
| 6 | nseq - create or examine a Netscape certificate sequence |
| 7 | |
| 8 | =head1 SYNOPSIS |
| 9 | |
| 10 | B<openssl> B<nseq> |
| 11 | [B<-help>] |
| 12 | [B<-in filename>] |
| 13 | [B<-out filename>] |
| 14 | [B<-toseq>] |
| 15 | |
| 16 | =head1 DESCRIPTION |
| 17 | |
| 18 | The B<nseq> command takes a file containing a Netscape certificate |
| 19 | sequence and prints out the certificates contained in it or takes a |
| 20 | file of certificates and converts it into a Netscape certificate |
| 21 | sequence. |
| 22 | |
| 23 | =head1 OPTIONS |
| 24 | |
| 25 | =over 4 |
| 26 | |
| 27 | =item B<-help> |
| 28 | |
| 29 | Print out a usage message. |
| 30 | |
| 31 | =item B<-in filename> |
| 32 | |
| 33 | This specifies the input filename to read or standard input if this |
| 34 | option is not specified. |
| 35 | |
| 36 | =item B<-out filename> |
| 37 | |
| 38 | Specifies the output filename or standard output by default. |
| 39 | |
| 40 | =item B<-toseq> |
| 41 | |
| 42 | Normally a Netscape certificate sequence will be input and the output |
| 43 | is the certificates contained in it. With the B<-toseq> option the |
| 44 | situation is reversed: a Netscape certificate sequence is created from |
| 45 | a file of certificates. |
| 46 | |
| 47 | =back |
| 48 | |
| 49 | =head1 EXAMPLES |
| 50 | |
| 51 | Output the certificates in a Netscape certificate sequence |
| 52 | |
| 53 | openssl nseq -in nseq.pem -out certs.pem |
| 54 | |
| 55 | Create a Netscape certificate sequence |
| 56 | |
| 57 | openssl nseq -in certs.pem -toseq -out nseq.pem |
| 58 | |
| 59 | =head1 NOTES |
| 60 | |
| 61 | The B<PEM> encoded form uses the same headers and footers as a certificate: |
| 62 | |
| 63 | -----BEGIN CERTIFICATE----- |
| 64 | -----END CERTIFICATE----- |
| 65 | |
| 66 | A Netscape certificate sequence is a Netscape specific format that can be sent |
| 67 | to browsers as an alternative to the standard PKCS#7 format when several |
| 68 | certificates are sent to the browser: for example during certificate enrollment. |
| 69 | It is used by Netscape certificate server for example. |
| 70 | |
| 71 | =head1 BUGS |
| 72 | |
| 73 | This program needs a few more options: like allowing DER or PEM input and |
| 74 | output files and allowing multiple certificate files to be used. |
| 75 | |
| 76 | =head1 COPYRIGHT |
| 77 | |
| 78 | Copyright 2000-2017 The OpenSSL Project Authors. All Rights Reserved. |
| 79 | |
| 80 | Licensed under the OpenSSL license (the "License"). You may not use |
| 81 | this file except in compliance with the License. You can obtain a copy |
| 82 | in the file LICENSE in the source distribution or at |
| 83 | L<https://www.openssl.org/source/license.html>. |
| 84 | |
| 85 | =cut |