1999-11-14 05:58:39 +08:00
|
|
|
=pod
|
|
|
|
|
|
|
|
|
|
=head1 NAME
|
|
|
|
|
|
2016-06-08 05:03:15 +08:00
|
|
|
nseq - create or examine a Netscape certificate sequence
|
1999-11-14 05:58:39 +08:00
|
|
|
|
|
|
|
|
=head1 SYNOPSIS
|
|
|
|
|
|
|
|
|
|
B<openssl> B<nseq>
|
2016-02-06 00:58:45 +08:00
|
|
|
[B<-help>]
|
1999-11-14 05:58:39 +08:00
|
|
|
[B<-in filename>]
|
|
|
|
|
[B<-out filename>]
|
|
|
|
|
[B<-toseq>]
|
|
|
|
|
|
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
|
|
|
|
|
|
The B<nseq> command takes a file containing a Netscape certificate
|
|
|
|
|
sequence and prints out the certificates contained in it or takes a
|
|
|
|
|
file of certificates and converts it into a Netscape certificate
|
|
|
|
|
sequence.
|
|
|
|
|
|
2016-12-13 00:14:40 +08:00
|
|
|
=head1 OPTIONS
|
1999-11-14 05:58:39 +08:00
|
|
|
|
|
|
|
|
=over 4
|
|
|
|
|
|
2016-02-06 00:58:45 +08:00
|
|
|
=item B<-help>
|
|
|
|
|
|
|
|
|
|
Print out a usage message.
|
|
|
|
|
|
1999-11-14 05:58:39 +08:00
|
|
|
=item B<-in filename>
|
|
|
|
|
|
|
|
|
|
This specifies the input filename to read or standard input if this
|
|
|
|
|
option is not specified.
|
|
|
|
|
|
|
|
|
|
=item B<-out filename>
|
|
|
|
|
|
2017-03-29 12:39:16 +08:00
|
|
|
Specifies the output filename or standard output by default.
|
1999-11-14 05:58:39 +08:00
|
|
|
|
|
|
|
|
=item B<-toseq>
|
|
|
|
|
|
2017-03-29 12:39:16 +08:00
|
|
|
Normally a Netscape certificate sequence will be input and the output
|
1999-11-14 05:58:39 +08:00
|
|
|
is the certificates contained in it. With the B<-toseq> option the
|
|
|
|
|
situation is reversed: a Netscape certificate sequence is created from
|
|
|
|
|
a file of certificates.
|
|
|
|
|
|
|
|
|
|
=back
|
|
|
|
|
|
|
|
|
|
=head1 EXAMPLES
|
|
|
|
|
|
|
|
|
|
Output the certificates in a Netscape certificate sequence
|
|
|
|
|
|
|
|
|
|
openssl nseq -in nseq.pem -out certs.pem
|
|
|
|
|
|
|
|
|
|
Create a Netscape certificate sequence
|
|
|
|
|
|
|
|
|
|
openssl nseq -in certs.pem -toseq -out nseq.pem
|
|
|
|
|
|
|
|
|
|
=head1 NOTES
|
|
|
|
|
|
|
|
|
|
The B<PEM> encoded form uses the same headers and footers as a certificate:
|
|
|
|
|
|
|
|
|
|
-----BEGIN CERTIFICATE-----
|
|
|
|
|
-----END CERTIFICATE-----
|
|
|
|
|
|
2017-03-29 12:39:16 +08:00
|
|
|
A Netscape certificate sequence is a Netscape specific format that can be sent
|
1999-11-14 05:58:39 +08:00
|
|
|
to browsers as an alternative to the standard PKCS#7 format when several
|
2000-01-07 09:39:59 +08:00
|
|
|
certificates are sent to the browser: for example during certificate enrollment.
|
1999-11-14 05:58:39 +08:00
|
|
|
It is used by Netscape certificate server for example.
|
|
|
|
|
|
|
|
|
|
=head1 BUGS
|
|
|
|
|
|
|
|
|
|
This program needs a few more options: like allowing DER or PEM input and
|
|
|
|
|
output files and allowing multiple certificate files to be used.
|
|
|
|
|
|
2016-05-18 23:44:05 +08:00
|
|
|
=head1 COPYRIGHT
|
|
|
|
|
|
2017-03-29 12:39:16 +08:00
|
|
|
Copyright 2000-2017 The OpenSSL Project Authors. All Rights Reserved.
|
2016-05-18 23:44:05 +08:00
|
|
|
|
|
|
|
|
Licensed under the OpenSSL license (the "License"). You may not use
|
|
|
|
|
this file except in compliance with the License. You can obtain a copy
|
|
|
|
|
in the file LICENSE in the source distribution or at
|
|
|
|
|
L<https://www.openssl.org/source/license.html>.
|
|
|
|
|
|
|
|
|
|
=cut
|
