Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
da45180d
T
Third Party Openssl
项目概览
OpenHarmony
/
Third Party Openssl
接近 2 年 前同步成功
通知
12
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看板
提交
da45180d
编写于
1月 26, 2003
作者:
D
Dr. Stephen Henson
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Correct EVP_SealInit() documentation, iv is an output
parameter.
上级
82516e3b
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
16 addition
and
10 deletion
+16
-10
doc/crypto/EVP_SealInit.pod
doc/crypto/EVP_SealInit.pod
+16
-10
未找到文件。
doc/crypto/EVP_SealInit.pod
浏览文件 @
da45180d
...
@@ -18,22 +18,28 @@ EVP_SealInit, EVP_SealUpdate, EVP_SealFinal - EVP envelope encryption
...
@@ -18,22 +18,28 @@ EVP_SealInit, EVP_SealUpdate, EVP_SealFinal - EVP envelope encryption
=head1 DESCRIPTION
=head1 DESCRIPTION
The EVP envelope routines are a high level interface to envelope
The EVP envelope routines are a high level interface to envelope
encryption. They generate a random key and
then "envelope" it by
encryption. They generate a random key and
IV (if required) then
using public key encryption. Data can then be encrypted using this
"envelope" it by using public key encryption. Data can then be
key.
encrypted using this
key.
EVP_SealInit() initializes a cipher context B<ctx> for encryption
EVP_SealInit() initializes a cipher context B<ctx> for encryption
with cipher B<type> using a random secret key and IV supplied in
with cipher B<type> using a random secret key and IV. B<type> is normally
the B<iv> parameter. B<type> is normally supplied by a function such
supplied by a function such as EVP_des_cbc(). The secret key is encrypted
as EVP_des_cbc(). The secret key is encrypted using one or more public
using one or more public keys, this allows the same encrypted data to be
keys, this allows the same encrypted data to be decrypted using any
decrypted using any of the corresponding private keys. B<ek> is an array of
of the corresponding private keys. B<ek> is an array of buffers where
buffers where the public key encrypted secret key will be written, each buffer
the public key encrypted secret key will be written, each buffer must
must contain enough room for the corresponding encrypted key: that is
contain enough room for the corresponding encrypted key: that is
B<ek[i]> must have room for B<EVP_PKEY_size(pubk[i])> bytes. The actual
B<ek[i]> must have room for B<EVP_PKEY_size(pubk[i])> bytes. The actual
size of each encrypted secret key is written to the array B<ekl>. B<pubk> is
size of each encrypted secret key is written to the array B<ekl>. B<pubk> is
an array of B<npubk> public keys.
an array of B<npubk> public keys.
The B<iv> parameter is a buffer where the generated IV is written to. It must
contain enough room for the corresponding cipher's IV, as determined by (for
example) EVP_CIPHER_iv_length(type).
If the cipher does not require an IV then the B<iv> parameter is ignored
and can be B<NULL>.
EVP_SealUpdate() and EVP_SealFinal() have exactly the same properties
EVP_SealUpdate() and EVP_SealFinal() have exactly the same properties
as the EVP_EncryptUpdate() and EVP_EncryptFinal() routines, as
as the EVP_EncryptUpdate() and EVP_EncryptFinal() routines, as
documented on the L<EVP_EncryptInit(3)|EVP_EncryptInit(3)> manual
documented on the L<EVP_EncryptInit(3)|EVP_EncryptInit(3)> manual
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录