Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
8a208cba
T
Third Party Openssl
项目概览
OpenHarmony
/
Third Party Openssl
1 年多 前同步成功
通知
9
Star
18
Fork
1
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
T
Third Party Openssl
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
提交
8a208cba
编写于
2月 18, 2000
作者:
D
Dr. Stephen Henson
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
New functions and option to use NEW in certificate requests.
上级
5c2ec54f
变更
7
隐藏空白更改
内联
并排
Showing
7 changed file
with
45 addition
and
12 deletion
+45
-12
CHANGES
CHANGES
+6
-0
apps/req.c
apps/req.c
+8
-4
crypto/pem/pem.h
crypto/pem/pem.h
+1
-0
crypto/pem/pem_all.c
crypto/pem/pem_all.c
+2
-0
doc/apps/req.pod
doc/apps/req.pod
+14
-8
util/libeay.num
util/libeay.num
+2
-0
util/mkdef.pl
util/mkdef.pl
+12
-0
未找到文件。
CHANGES
浏览文件 @
8a208cba
...
...
@@ -4,6 +4,12 @@
Changes between 0.9.4 and 0.9.5 [xx XXX 2000]
*) Add some PEM_write_X509_REQ_NEW() functions and a command line
argument to 'req'. This is not because the function is newer or
better than others it just uses the work 'NEW' in the certificate
request header lines. Some software needs this.
[Steve Henson]
*) Reorganise password command line arguments: now passwords can be
obtained from various sources. Delete the PEM_cb function and make
it the default behaviour: i.e. if the callback is NULL and the
...
...
apps/req.c
浏览文件 @
8a208cba
...
...
@@ -150,7 +150,7 @@ int MAIN(int argc, char **argv)
int
i
,
badops
=
0
,
newreq
=
0
,
newkey
=
-
1
,
pkey_type
=
0
;
BIO
*
in
=
NULL
,
*
out
=
NULL
;
int
informat
,
outformat
,
verify
=
0
,
noout
=
0
,
text
=
0
,
keyform
=
FORMAT_PEM
;
int
nodes
=
0
,
kludge
=
0
;
int
nodes
=
0
,
kludge
=
0
,
newhdr
=
0
;
char
*
infile
,
*
outfile
,
*
prog
,
*
keyfile
=
NULL
,
*
template
=
NULL
,
*
keyout
=
NULL
;
char
*
extensions
=
NULL
;
char
*
req_exts
=
NULL
;
...
...
@@ -306,6 +306,8 @@ int MAIN(int argc, char **argv)
newreq
=
1
;
}
else
if
(
strcmp
(
*
argv
,
"-newhdr"
)
==
0
)
newhdr
=
1
;
else
if
(
strcmp
(
*
argv
,
"-modulus"
)
==
0
)
modulus
=
1
;
else
if
(
strcmp
(
*
argv
,
"-verify"
)
==
0
)
...
...
@@ -378,6 +380,7 @@ bad:
BIO_printf
(
bio_err
,
" -new new request.
\n
"
);
BIO_printf
(
bio_err
,
" -x509 output a x509 structure instead of a cert. req.
\n
"
);
BIO_printf
(
bio_err
,
" -days number of days a x509 generated by -x509 is valid for.
\n
"
);
BIO_printf
(
bio_err
,
" -newhdr output
\"
NEW
\"
in the header lines
\n
"
);
BIO_printf
(
bio_err
,
" -asn1-kludge Output the 'request' in a format that is wrong but some CA's
\n
"
);
BIO_printf
(
bio_err
,
" have been reported as requiring
\n
"
);
BIO_printf
(
bio_err
,
" -extensions .. specify certificate extension section (override value in config file)
\n
"
);
...
...
@@ -834,9 +837,10 @@ loop:
{
if
(
outformat
==
FORMAT_ASN1
)
i
=
i2d_X509_REQ_bio
(
out
,
req
);
else
if
(
outformat
==
FORMAT_PEM
)
i
=
PEM_write_bio_X509_REQ
(
out
,
req
);
else
{
else
if
(
outformat
==
FORMAT_PEM
)
{
if
(
newhdr
)
i
=
PEM_write_bio_X509_REQ_NEW
(
out
,
req
);
else
i
=
PEM_write_bio_X509_REQ
(
out
,
req
);
}
else
{
BIO_printf
(
bio_err
,
"bad output format specified for outfile
\n
"
);
goto
end
;
}
...
...
crypto/pem/pem.h
浏览文件 @
8a208cba
...
...
@@ -534,6 +534,7 @@ DECLARE_PEM_rw(X509, X509)
DECLARE_PEM_rw
(
X509_AUX
,
X509
)
DECLARE_PEM_rw
(
X509_REQ
,
X509_REQ
)
DECLARE_PEM_write
(
X509_REQ_NEW
,
X509_REQ
)
DECLARE_PEM_rw
(
X509_CRL
,
X509_CRL
)
...
...
crypto/pem/pem_all.c
浏览文件 @
8a208cba
...
...
@@ -78,6 +78,8 @@ IMPLEMENT_PEM_rw(X509_AUX, X509, PEM_STRING_X509_TRUSTED, X509_AUX)
IMPLEMENT_PEM_rw
(
X509_REQ
,
X509_REQ
,
PEM_STRING_X509_REQ
,
X509_REQ
)
IMPLEMENT_PEM_write
(
X509_REQ_NEW
,
X509_REQ
,
PEM_STRING_X509_REQ_OLD
,
X509_REQ
)
IMPLEMENT_PEM_rw
(
X509_CRL
,
X509_CRL
,
PEM_STRING_X509_CRL
,
X509_CRL
)
IMPLEMENT_PEM_rw
(
PKCS7
,
PKCS7
,
PEM_STRING_PKCS7
,
PKCS7
)
...
...
doc/apps/req.pod
浏览文件 @
8a208cba
...
...
@@ -29,7 +29,8 @@ B<openssl> B<req>
[B<-config filename>]
[B<-x509>]
[B<-days n>]
[B<-noasn1-kludge>]
[B<-asn1-kludge>]
[B<-newhdr>]
[B<-extensions section>]
[B<-reqexts section>]
...
...
@@ -180,6 +181,11 @@ B<SET OF> whereas the correct form does.
It should be noted that very few CAs still require the use of this option.
=item B<-newhdr>
Adds the word B<NEW> to the PEM file header and footer lines on the outputed
request. Some software (Netscape certificate server) and some CAs need this.
=back
=head1 CONFIGURATION FILE FORMAT
...
...
@@ -302,9 +308,9 @@ just consist of field names and values: for example,
This allows external programs (e.g. GUI based) to generate a template file
with all the field names and values and just pass it to B<req>. An example
of this kind of configuration file
s
is contained in the B<EXAMPLES> section.
of this kind of configuration file is contained in the B<EXAMPLES> section.
Alternatively if the B<prompt> option is absent or not set to B<no> the the
Alternatively if the B<prompt> option is absent or not set to B<no> the
n
the
file contains field prompting information. It consists of lines of the form:
fieldName="prompt"
...
...
@@ -327,7 +333,7 @@ two characters long and must fit in a PrintableString).
Some fields (such as organizationName) can be used more than once
in a DN. This presents a problem because configuration files will
not recognize the same name occurring twice. To avoid this problem
if the fieldName contains
an
some characters followed by a full stop
if the fieldName contains some characters followed by a full stop
they will be ignored. So for example a second organizationName can
be input by calling it "1.organizationName".
...
...
@@ -335,8 +341,7 @@ The actual permitted field names are any object identifier short or
long names. These are compiled into OpenSSL and include the usual
values such as commonName, countryName, localityName, organizationName,
organizationUnitName, stateOrPrivinceName. Additionally emailAddress
is include as well as name, surname, givenName initials and dnQualifier
are supported.
is include as well as name, surname, givenName initials and dnQualifier.
Additional object identifiers can be defined with the B<oid_file> or
B<oid_section> options in the configuration file. Any additional fields
...
...
@@ -439,7 +444,7 @@ Sample configuration containing all field values:
=head1 NOTES
The header and footer lines in the B<PEM> format are
respective
ly:
The header and footer lines in the B<PEM> format are
normal
ly:
-----BEGIN CERTIFICATE REQUEST----
-----END CERTIFICATE REQUEST----
...
...
@@ -449,7 +454,8 @@ 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.
which is produced with the B<-newhdr> option but is otherwise compatible.
Either form is accepted transparently 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
...
...
util/libeay.num
浏览文件 @
8a208cba
...
...
@@ -2222,3 +2222,5 @@ CRYPTO_dbg_get_options 2246
AUTHORITY_INFO_ACCESS_new 2247
CRYPTO_get_mem_debug_options 2248
des_crypt 2249
PEM_write_bio_X509_REQ_NEW 2250
PEM_write_X509_REQ_NEW 2251
util/mkdef.pl
浏览文件 @
8a208cba
...
...
@@ -301,6 +301,18 @@ sub do_defs
}
$funcs
{"
PEM_read_bio_
${
1
}
"}
=
1
;
$funcs
{"
PEM_write_bio_
${
1
}
"}
=
1
;
}
elsif
(
/^DECLARE_PEM_write\s*\(\s*(\w*)\s*,/
||
/^DECLARE_PEM_write_cb\s*\(\s*(\w*)\s*,/
)
{
if
(
$W32
)
{
$funcs
{"
PEM_write_
${
1
}
"}
=
1
;
}
$funcs
{"
PEM_write_bio_
${
1
}
"}
=
1
;
}
elsif
(
/^DECLARE_PEM_read\s*\(\s*(\w*)\s*,/
||
/^DECLARE_PEM_read_cb\s*\(\s*(\w*)\s*,/
)
{
if
(
$W32
)
{
$funcs
{"
PEM_read_
${
1
}
"}
=
1
;
}
$funcs
{"
PEM_read_bio_
${
1
}
"}
=
1
;
}
elsif
(
(
$tag
{'
TRUE
'}
!=
-
1
)
&&
(
$tag
{'
FreeBSD
'}
!=
1
)
&&
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录