Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
btwise
openssl
提交
0286d944
O
openssl
项目概览
btwise
/
openssl
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
O
openssl
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
0286d944
编写于
11月 13, 1999
作者:
D
Dr. Stephen Henson
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add info about the header and footer lines used in PEM formats
and add an nseq manpage.
上级
938ead8f
变更
7
隐藏空白更改
内联
并排
Showing
7 changed file
with
123 addition
and
5 deletion
+123
-5
doc/man/dsa.pod
doc/man/dsa.pod
+7
-0
doc/man/dsaparam.pod
doc/man/dsaparam.pod
+5
-0
doc/man/nseq.pod
doc/man/nseq.pod
+70
-0
doc/man/pkcs8.pod
doc/man/pkcs8.pod
+11
-0
doc/man/req.pod
doc/man/req.pod
+11
-5
doc/man/rsa.pod
doc/man/rsa.pod
+7
-0
doc/man/x509.pod
doc/man/x509.pod
+12
-0
未找到文件。
doc/man/dsa.pod
浏览文件 @
0286d944
...
...
@@ -117,6 +117,13 @@ a public key.
=back
=head1 NOTES
The PEM private key format uses the header and footer lines:
-----BEGIN DSA PRIVATE KEY-----
-----END DSA PRIVATE KEY-----
=head1 EXAMPLES
To remove the pass phrase on a DSA private key:
...
...
doc/man/dsaparam.pod
浏览文件 @
0286d944
...
...
@@ -82,6 +82,11 @@ the input file (if any) is ignored.
=head1 NOTES
PEM format DSA parameters use the header and footer lines:
-----BEGIN DSA PARAMETERS-----
-----END DSA PARAMETERS-----
DSA parameter generation is a slow process and as a result the same set of
DSA parameters is often used to generate several distinct keys.
...
...
doc/man/nseq.pod
0 → 100644
浏览文件 @
0286d944
=pod
=head1 NAME
nseq - create or examine a netscape certificate sequence
=head1 SYNOPSIS
B<openssl> B<nseq>
[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.
=head1 COMMAND OPTIONS
=over 4
=item B<-in filename>
This specifies the input filename to read or standard input if this
option is not specified.
=item B<-out filename>
specifies the output filename or standard output by default.
=item B<-toseq>
normally a Netscape certificate sequence will be input and the output
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-----
A Netscape certificate sequence is a Netscape specific form that can be sent
to browsers as an alternative to the standard PKCS#7 format when several
certificates are sent to the browser: for example during certificate erollment.
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.
=cut
doc/man/pkcs8.pod
浏览文件 @
0286d944
...
...
@@ -93,6 +93,17 @@ B<des>, B<des3> and B<rc2>. It is recommended that B<des3> is used.
=head1 NOTES
The encrypted form of a PEM encode PKCS#8 files uses the following
headers and footers:
-----BEGIN ENCRYPTED PRIVATE KEY-----
-----END ENCRYPTED PRIVATE KEY-----
The unencrypted form uses:
-----BEGIN PRIVATE KEY-----
-----END PRIVATE KEY-----
Private keys encrypted using PKCS#5 v2.0 algorithms and high iteration
counts are more secure that those encrypted using the traditional
SSLeay compatible formats. So if additional security is considered
...
...
doc/man/req.pod
浏览文件 @
0286d944
...
...
@@ -371,11 +371,17 @@ Sample configuration file:
=head1 NOTES
The header and footer lines in the B<PEM> format contain the words
B<BEGIN CERTIFICATE REQUEST> and B<END CERTIFICATE REQUEST> some software
(for example some versions of Netscape certificate server) requires the
words B<BEGIN NEW CERTIFICATE REQUEST> and B<END NEW CERTIFICATE REQUEST>
instead.
The header and footer lines in the B<PEM> format are respectively:
-----BEGIN CERTIFICATE REQUEST----
-----END CERTIFICATE REQUEST----
some software (some versions of Netscape certificate server) instead needs:
-----BEGIN NEW CERTIFICATE REQUEST----
-----END NEW CERTIFICATE REQUEST----
but is otherwise compatible. Either form is accepted on input.
The certificate requests generated by B<Xenroll> with MSIE have extensions
added. It includes the B<keyUsage> extension which determines the type of
...
...
doc/man/rsa.pod
浏览文件 @
0286d944
...
...
@@ -123,6 +123,13 @@ a public key.
=back
=head1 NOTES
The PEM private key format uses the header and footer lines:
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
=head1 EXAMPLES
To remove the pass phrase on an RSA private key:
...
...
doc/man/x509.pod
浏览文件 @
0286d944
...
...
@@ -371,6 +371,18 @@ Set a certificate to be trusted for SSL client use and change set its alias to
openssl x509 -in cert.pem -addtrust sslclient \
-alias "Steve's Class 1 CA" -out trust.pem
=head1 NOTES
The PEM format uses the header and footer lines:
-----BEGIN CERTIFICATE----
-----END CERTIFICATE----
it will also handle files containing:
-----BEGIN X509 CERTIFICATE----
-----END X509 CERTIFICATE----
=head1 BUGS
The way DNs are printed is in a "historical SSLeay" format which doesn't
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录