Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
c420fab5
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看板
体验新版 GitCode,发现更多精彩内容 >>
提交
c420fab5
编写于
4月 10, 2008
作者:
D
Dr. Stephen Henson
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Spellcheck CMS docs.
上级
6469a1fd
变更
11
显示空白变更内容
内联
并排
Showing
11 changed file
with
17 addition
and
17 deletion
+17
-17
doc/crypto/CMS_add1_recipient_cert.pod
doc/crypto/CMS_add1_recipient_cert.pod
+1
-1
doc/crypto/CMS_decrypt.pod
doc/crypto/CMS_decrypt.pod
+1
-1
doc/crypto/CMS_encrypt.pod
doc/crypto/CMS_encrypt.pod
+1
-1
doc/crypto/CMS_get0_RecipientInfos.pod
doc/crypto/CMS_get0_RecipientInfos.pod
+2
-2
doc/crypto/CMS_get0_SignerInfos.pod
doc/crypto/CMS_get0_SignerInfos.pod
+1
-1
doc/crypto/CMS_get0_type.pod
doc/crypto/CMS_get0_type.pod
+2
-2
doc/crypto/CMS_get1_ReceiptRequest.pod
doc/crypto/CMS_get1_ReceiptRequest.pod
+1
-1
doc/crypto/CMS_sign.pod
doc/crypto/CMS_sign.pod
+2
-2
doc/crypto/CMS_sign_add1_signer.pod
doc/crypto/CMS_sign_add1_signer.pod
+2
-2
doc/crypto/CMS_verify.pod
doc/crypto/CMS_verify.pod
+3
-3
doc/crypto/SMIME_write_CMS.pod
doc/crypto/SMIME_write_CMS.pod
+1
-1
未找到文件。
doc/crypto/CMS_add1_recipient_cert.pod
浏览文件 @
c420fab5
...
...
@@ -20,7 +20,7 @@ structure.
CMS_add0_recipient_key() adds symmetric key B<key> of length B<keylen> using
wrapping algorithm B<nid>, identifier B<id> or length B<idlen> and optional
values B<date>, B<otherTypeId> a
b
d B<otherType> to CMS_ContentInfo enveloped
values B<date>, B<otherTypeId> a
n
d B<otherType> to CMS_ContentInfo enveloped
data structure B<cms> as a KEKRecipientInfo structure.
The CMS_ContentInfo structure should be obtained from an initial call to
...
...
doc/crypto/CMS_decrypt.pod
浏览文件 @
c420fab5
...
...
@@ -30,7 +30,7 @@ needed to locate the appropriate (of possible several) recipients in the CMS
structure. If B<cert> is set to NULL all possible recipients are tried.
It is possible to determine the correct recipient key by other means (for
example looking them up in a database) and settin
them in the CMS strutuc
re
example looking them up in a database) and settin
g them in the CMS structu
re
in advance using the CMS utility functions such as CMS_set1_pkey(). In this
case both B<cert> and B<pkey> should be set to NULL.
...
...
doc/crypto/CMS_encrypt.pod
浏览文件 @
c420fab5
...
...
@@ -76,7 +76,7 @@ PEM_write_bio_CMS_stream() finalize the structure. Alternatively finalization
can be performed by obtaining the streaming ASN1 B<BIO> directly using
BIO_new_CMS().
The rec
e
ipients specified in B<certs> use a CMS KeyTransRecipientInfo info
The recipients specified in B<certs> use a CMS KeyTransRecipientInfo info
structure. KEKRecipientInfo is also supported using the flag B<CMS_PARTIAL>
and CMS_add0_recipient_key().
...
...
doc/crypto/CMS_get0_RecipientInfos.pod
浏览文件 @
c420fab5
...
...
@@ -35,7 +35,7 @@ identifier associated with a specific CMS_RecipientInfo structure B<ri>, which
must be of type CMS_RECIPINFO_TRANS. Either the keyidentifier will be set in
B<keyid> or B<both> issuer name and serial number in B<issuer> and B<sno>.
CMS_RecipientInfo_ktri_cert_cmp() compares the cerificate B<cert> against the
CMS_RecipientInfo_ktri_cert_cmp() compares the cer
t
ificate B<cert> against the
CMS_RecipientInfo structure B<ri>, which must be of type CMS_RECIPINFO_TRANS.
It returns zero if the comparison is successful and non zero if not.
...
...
@@ -91,7 +91,7 @@ CMS_RecipientInfo_kekri_get0_id(), CMS_RecipientInfo_set0_key() and
CMS_RecipientInfo_decrypt() return 1 for success or 0 if an error occurs.
CMS_RecipientInfo_ktri_cert_cmp() and CMS_RecipientInfo_kekri_cmp() return 0
for a successul comparison and non zero otherwise.
for a success
f
ul comparison and non zero otherwise.
Any error can be obtained from L<ERR_get_error(3)|ERR_get_error(3)>.
...
...
doc/crypto/CMS_get0_SignerInfos.pod
浏览文件 @
c420fab5
...
...
@@ -26,7 +26,7 @@ associated with a specific CMS_SignerInfo structure B<si>. Either the
keyidentifier will be set in B<keyid> or B<both> issuer name and serial number
in B<issuer> and B<sno>.
CMS_SignerInfo_cert_cmp() compares the cerificate B<cert> against the signer
CMS_SignerInfo_cert_cmp() compares the cer
t
ificate B<cert> against the signer
identifier B<si>. It returns zero if the comparison is successful and non zero
if not.
...
...
doc/crypto/CMS_get0_type.pod
浏览文件 @
c420fab5
...
...
@@ -16,11 +16,11 @@
CMS_get0_type() returns the content type of a CMS_ContentInfo structure as
and ASN1_OBJECT pointer. An application can then decide how to process the
CMS_ContentInfo stru
tu
cture based on this value.
CMS_ContentInfo structure based on this value.
CMS_set1_eContentType() sets the embedded content type of a CMS_ContentInfo
structure. It should be called with CMS functions with the B<CMS_PARTIAL>
flag and B<before> the stru
tuc
re is finalised, otherwise the results are
flag and B<before> the stru
ctu
re is finalised, otherwise the results are
undefined.
ASN1_OBJECT *CMS_get0_eContentType() returns a pointer to the embedded
...
...
doc/crypto/CMS_get1_ReceiptRequest.pod
浏览文件 @
c420fab5
...
...
@@ -24,7 +24,7 @@ option in B<receiptsFrom> is used. The B<receiptsTo> parameter specifies the
B<receiptsTo> field value.
The CMS_add1_ReceiptRequest() function adds a signed receipt request B<rr>
to SignerInfo stru
tuc
re B<si>.
to SignerInfo stru
ctu
re B<si>.
int CMS_get1_ReceiptRequest() looks for a signed receipt request in B<si>, if
any is found it is decoded and written to B<prr>.
...
...
doc/crypto/CMS_sign.pod
浏览文件 @
c420fab5
...
...
@@ -13,7 +13,7 @@ CMS_sign - create a CMS SignedData structure
=head1 DESCRIPTION
CMS_sign() creates and returns a CMS SignedData structure. B<signcert> is
the certificate to sign with, B<pkey> is the correspon
s
ding private key.
the certificate to sign with, B<pkey> is the corresponding private key.
B<certs> is an optional additional set of certificates to include in the CMS
structure (for example any intermediate CAs in the chain). Any or all of
these parameters can be B<NULL>, see B<NOTES> below.
...
...
@@ -114,6 +114,6 @@ L<ERR_get_error(3)|ERR_get_error(3)>, L<CMS_verify(3)|CMS_verify(3)>
CMS_sign() was added to OpenSSL 0.9.8
The B<CMS_STREAM> flag is only supported for detached data in OpenSSL 0.9.8,
it is supportd for embedded data in OpenSSL 0.9.9 and later.
it is support
e
d for embedded data in OpenSSL 0.9.9 and later.
=cut
doc/crypto/CMS_sign_add1_signer.pod
浏览文件 @
c420fab5
...
...
@@ -40,14 +40,14 @@ The main purpose of this CMS_sign_add1_signer() is to provide finer control
over a CMS signed data structure where the simpler CMS_sign() function defaults
are not appropriate. For example if multiple signers or non default digest
algorithms are needed. New attributes can also be added using the returned
CMS_SignerInfo struture and the CMS attribute utility functions or the
CMS_SignerInfo stru
c
ture and the CMS attribute utility functions or the
CMS signed receipt request functions.
Any of the following flags (ored together) can be passed in the B<flags>
parameter.
If B<CMS_REUSE_DIGEST> is set then an attempt is made to copy the content
digest value from the CMS_ContentInfo struture: to add a signer to an existing
digest value from the CMS_ContentInfo stru
c
ture: to add a signer to an existing
structure. An error occurs if a matching digest value cannot be found to copy.
The returned CMS_ContentInfo structure will be valid and finalized when this
flag is set.
...
...
doc/crypto/CMS_verify.pod
浏览文件 @
c420fab5
...
...
@@ -16,7 +16,7 @@ CMS_verify - verify a CMS SignedData structure
CMS_verify() verifies a CMS SignedData structure. B<cms> is the CMS_ContentInfo
structure to verify. B<certs> is a set of certificates in which to search for
the signer's certificate. B<store> is a trusted certficate store (used for
the signer's certificate. B<store> is a trusted cert
i
ficate store (used for
chain verification). B<indata> is the signed data if the content is not
present in B<cms> (that is it is detached). The content is written to B<out>
if it is not NULL.
...
...
@@ -25,7 +25,7 @@ B<flags> is an optional set of flags, which can be used to modify the verify
operation.
CMS_get0_signers() retrieves the signer's certificate(s) from B<cms>, it must
be called after a succeful CMS_verify() operation.
be called after a succe
ss
ful CMS_verify() operation.
=head1 VERIFY PROCESS
...
...
@@ -101,7 +101,7 @@ timestamp).
=head1 RETURN VALUES
CMS_verify() returns 1 for a successful verification and zero if an error
occured.
occur
r
ed.
CMS_get0_signers() returns all signers or B<NULL> if an error occurred.
...
...
doc/crypto/SMIME_write_CMS.pod
浏览文件 @
c420fab5
...
...
@@ -40,7 +40,7 @@ the data must be read twice: once to compute the signature in CMS_sign()
and once to output the S/MIME message.
If streaming is performed the content is output in BER format using indefinite
length construct
ut
ed encoding except in the case of signed data with detached
length constructed encoding except in the case of signed data with detached
content where the content is absent and DER format is used.
=head1 BUGS
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录