Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
4c5e6b2c
T
Third Party Openssl
项目概览
OpenHarmony
/
Third Party Openssl
10 个月 前同步成功
通知
8
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,体验更适合开发者的 AI 搜索 >>
提交
4c5e6b2c
编写于
4月 26, 2016
作者:
R
Richard Levitte
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Documentation the changed {RSA,DSA,DH}_set0_* functionality change
Reviewed-by:
N
Matt Caswell
<
matt@openssl.org
>
上级
1da12e34
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
35 addition
and
6 deletion
+35
-6
doc/crypto/DH_get0_pqg.pod
doc/crypto/DH_get0_pqg.pod
+10
-1
doc/crypto/DSA_get0_pqg.pod
doc/crypto/DSA_get0_pqg.pod
+10
-1
doc/crypto/RSA_get0_key.pod
doc/crypto/RSA_get0_key.pod
+15
-4
未找到文件。
doc/crypto/DH_get0_pqg.pod
浏览文件 @
4c5e6b2c
...
...
@@ -47,7 +47,9 @@ be. The values point to the internal representation of the public key and
private key values. This memory should not be freed directly.
The public and private key values can be set using DH_set0_key(). The public
key must always be non-NULL. The private key may be NULL. As for DH_set0_pqg()
key must be non-NULL the first time this function is called on a given DH
object. The private key may be NULL. On subsequent calls, either may be NULL,
which means the corresponding DH field is left untouched. As for DH_set0_pqg()
this function transfers the memory management of the key values to the DH
object, and therefore they should not be freed directly after this function has
been called.
...
...
@@ -68,6 +70,13 @@ length parameter associated with this DH object. If the length is non-zero then
it is used, otherwise it is ignored. The B<length> parameter indicates the
length of the secret exponent (private key) in bits.
=head1 NOTES
Values retrieved with DH_get0_key() are owned by the DH object used
in the call and may therefore I<not> be passed to DH_set0_key(). If
needed, duplicate the received value using BN_dup() and pass the
duplicate. The same applies to DH_get0_pqg() and DH_set0_pqg().
=head1 RETURN VALUES
DH_set0_pqg() and DH_set0_key() return 1 on success or 0 on failure.
...
...
doc/crypto/DSA_get0_pqg.pod
浏览文件 @
4c5e6b2c
...
...
@@ -44,7 +44,9 @@ be. The values point to the internal representation of the public key and
private key values. This memory should not be freed directly.
The public and private key values can be set using DSA_set0_key(). The public
key must always be non-NULL. The private key may be NULL. As for DSA_set0_pqg()
key must be non-NULL the first time this function is called on a given DSA
object. The private key may be NULL. On subsequent calls, either may be NULL,
which means the corresponding DSA field is left untouched. As for DSA_set0_pqg()
this function transfers the memory management of the key values to the DSA
object, and therefore they should not be freed directly after this function has
been called.
...
...
@@ -60,6 +62,13 @@ within the DSA object.
DSA_get0_engine() returns a handle to the ENGINE that has been set for this DSA
object, or NULL if no such ENGINE has been set.
=head1 NOTES
Values retrieved with DSA_get0_key() are owned by the DSA object used
in the call and may therefore I<not> be passed to DSA_set0_key(). If
needed, duplicate the received value using BN_dup() and pass the
duplicate. The same applies to DSA_get0_pqg() and DSA_set0_pqg().
=head1 RETURN VALUES
DSA_set0_pqg() and DSA_set0_key() return 1 on success or 0 on failure.
...
...
doc/crypto/RSA_get0_key.pod
浏览文件 @
4c5e6b2c
...
...
@@ -43,10 +43,13 @@ by the caller.
The B<n>, B<e> and B<d> parameter values can be set by calling
RSA_set0_key() and passing the new values for B<n>, B<e> and B<d> as
parameters to the function. Calling this function transfers the memory
management of the values to the RSA object, and therefore the values
that have been passed in should not be freed by the caller after this
function has been called.
parameters to the function. The values B<n> and B<e> must be non-NULL
the first time this function is called on a given RSA object. The
value B<d> may be NULL. On subsequent calls any of these values may be
NULL which means the corresponding RSA field is left untouched.
Calling this function transfers the memory management of the values to
the RSA object, and therefore the values that have been passed in
should not be freed by the caller after this function has been called.
In a similar fashion, the B<p> and B<q> parameters can be obtained and
set with RSA_get0_factors() and RSA_set0_factors(), and the B<dmp1>,
...
...
@@ -65,6 +68,14 @@ RSA object.
RSA_get0_engine() returns a handle to the ENGINE that has been set for
this RSA object, or NULL if no such ENGINE has been set.
=head1 NOTES
Values retrieved with RSA_get0_key() are owned by the RSA object used
in the call and may therefore I<not> be passed to RSA_set0_key(). If
needed, duplicate the received value using BN_dup() and pass the
duplicate. The same applies to RSA_get0_factors() and RSA_set0_factors()
as well as RSA_get0_crt_params() and RSA_set0_crt_params().
=head1 RETURN VALUES
RSA_set0_key(), RSA_set0_factors and RSA_set0_crt_params() return 1 on
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录