Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
924875e5
T
Third Party Openssl
项目概览
OpenHarmony
/
Third Party Openssl
1 年多 前同步成功
通知
10
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看板
提交
924875e5
编写于
7月 27, 2001
作者:
B
Bodo Möller
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Undo DH_generate_key() change: s3_srvr.c was using it correctly
上级
3a644582
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
9 addition
and
16 deletion
+9
-16
CHANGES
CHANGES
+0
-11
crypto/dh/dh_key.c
crypto/dh/dh_key.c
+6
-1
doc/crypto/DH_generate_key.pod
doc/crypto/DH_generate_key.pod
+3
-4
未找到文件。
CHANGES
浏览文件 @
924875e5
...
...
@@ -26,17 +26,6 @@
This made problems when used from OpenSSH.
[Lutz Jaenicke]
*) In crypto/dh/dh_key.c, change generate_key() (the default
implementation of DH_generate_key()) so that a new key is
generated each time DH_generate_key() is used on a DH object.
Previously, DH_generate_key() did not change existing keys
-- but ssl/s3_srvr.c always expected it to do so (in effect,
SSL_OP_SINGLE_DH_USE was ignored in servers reusing the same SSL
object for multiple connections; however, each new SSL object
created from an SSL_CTX got its own key).
[Bodo Moeller]
*) In OpenSSL 0.9.6a and 0.9.6b, crypto/dh/dh_key.c ignored
dh->length and always used
...
...
crypto/dh/dh_key.c
浏览文件 @
924875e5
...
...
@@ -101,6 +101,7 @@ const DH_METHOD *DH_OpenSSL(void)
static
int
generate_key
(
DH
*
dh
)
{
int
ok
=
0
;
int
generate_new_key
=
0
;
unsigned
l
;
BN_CTX
*
ctx
;
BN_MONT_CTX
*
mont
;
...
...
@@ -113,6 +114,7 @@ static int generate_key(DH *dh)
{
priv_key
=
BN_new
();
if
(
priv_key
==
NULL
)
goto
err
;
generate_new_key
=
1
;
}
else
priv_key
=
dh
->
priv_key
;
...
...
@@ -135,7 +137,10 @@ static int generate_key(DH *dh)
l
=
dh
->
length
?
dh
->
length
:
BN_num_bits
(
dh
->
p
)
-
1
;
/* secret exponent length */
if
(
!
BN_rand
(
priv_key
,
l
,
0
,
0
))
goto
err
;
if
(
generate_new_key
)
{
if
(
!
BN_rand
(
priv_key
,
l
,
0
,
0
))
goto
err
;
}
if
(
!
ENGINE_get_DH
(
dh
->
engine
)
->
bn_mod_exp
(
dh
,
pub_key
,
dh
->
g
,
priv_key
,
dh
->
p
,
ctx
,
mont
))
goto
err
;
...
...
doc/crypto/DH_generate_key.pod
浏览文件 @
924875e5
...
...
@@ -21,8 +21,9 @@ value to compute the shared key.
DH_generate_key() expects B<dh> to contain the shared parameters
B<dh-E<gt>p> and B<dh-E<gt>g>. It generates a random private DH value
B<dh-E<gt>priv_key>, and it computes the corresponding public value
B<dh-E<gt>pub_key>, which can then be published.
unless B<dh-E<gt>priv_key> is already set, and computes the
corresponding public value B<dh-E<gt>pub_key>, which can then be
published.
DH_compute_key() computes the shared secret from the private DH value
in B<dh> and the other party's public value in B<pub_key> and stores
...
...
@@ -45,7 +46,5 @@ L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<DH_size(3)|DH_size(3)>
DH_generate_key() and DH_compute_key() are available in all versions
of SSLeay and OpenSSL.
Up to version 0.9.6b, DH_generate_key() would not generate a new
key if B<dh-E<gt>priv_key> was already set.
=cut
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录