Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
5812e6f1
T
Third Party Openssl
项目概览
OpenHarmony
/
Third Party Openssl
11 个月 前同步成功
通知
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,发现更多精彩内容 >>
提交
5812e6f1
编写于
4月 13, 2015
作者:
A
Alok Menghrajani
提交者:
Rich Salz
5月 03, 2015
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Fixes some typos in doc/ssl/
This is the last of Alok's PR260 Reviewed-by:
N
Tim Hudson
<
tjh@openssl.org
>
上级
4c583c36
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
15 addition
and
15 deletion
+15
-15
doc/ssl/SSL_CTX_set_cert_cb.pod
doc/ssl/SSL_CTX_set_cert_cb.pod
+1
-1
doc/ssl/SSL_CTX_set_security_level.pod
doc/ssl/SSL_CTX_set_security_level.pod
+1
-1
doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod
doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod
+13
-13
未找到文件。
doc/ssl/SSL_CTX_set_cert_cb.pod
浏览文件 @
5812e6f1
...
...
@@ -43,7 +43,7 @@ SSL_add1_chain_cert().
It might also call SSL_certs_clear() to delete any certificates associated
with the B<SSL> object.
The certificate callback functionality super
c
edes the (largely broken)
The certificate callback functionality super
s
edes the (largely broken)
functionality provided by the old client certificate callback interface.
It is B<always> called even is a certificate is already set so the callback
can modify or delete the existing certificate.
...
...
doc/ssl/SSL_CTX_set_security_level.pod
浏览文件 @
5812e6f1
...
...
@@ -34,7 +34,7 @@ SSL_CTX_set_security_level, SSL_set_security_level, SSL_CTX_get_security_level,
=head1 DESCRIPTION
The functions SSL_CTX_set_security_level() and SSL_set_security_level() set
the security level to B<level>. If not set the libary default security level
the security level to B<level>. If not set the lib
r
ary default security level
is used.
The functions SSL_CTX_get_security_level() and SSL_get_security_level()
...
...
doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod
浏览文件 @
5812e6f1
...
...
@@ -15,7 +15,7 @@ SSL_CTX_set_tlsext_ticket_key_cb - set a callback for session ticket processing
=head1 DESCRIPTION
SSL_CTX_set_tlsext_ticket_key_cb() sets a callback fu
ction I<cb> for handling
SSL_CTX_set_tlsext_ticket_key_cb() sets a callback fu
nction I<cb> for handling
session tickets for the ssl context I<sslctx>. Session tickets, defined in
RFC5077 provide an enhanced session resumption capability where the server
implementation is not required to maintain per session state. It only applies
...
...
@@ -40,13 +40,13 @@ The server, through the callback function, either agrees to reuse the session
ticket information or it starts a full TLS handshake to create a new session
ticket.
Before the callback function is started I<ctx> and I<hctx> have been
Before the callback function is started I<ctx> and I<hctx> have been
initialised with EVP_CIPHER_CTX_init and HMAC_CTX_init respectively.
For new sessions tickets, when the client doesn't present a session ticket, or
an attempted retr
ei
val of the ticket failed, or a renew option was indicated,
an attempted retr
ie
val of the ticket failed, or a renew option was indicated,
the callback function will be called with I<enc> equal to 1. The OpenSSL
library expects that the function will set an arbitary I<name>, initialize
library expects that the function will set an arbit
r
ary I<name>, initialize
I<iv>, and set the cipher context I<ctx> and the hash context I<hctx>.
The I<name> is 16 characters long and is used as a key identifier.
...
...
@@ -54,22 +54,22 @@ The I<name> is 16 characters long and is used as a key identifier.
The I<iv> length is the length of the IV of the corresponding cipher. The
maximum IV length is L<EVP_MAX_IV_LENGTH> bytes defined in B<evp.h>.
The initialization vector I<iv> should be a random value. The cipher context
I<ctx> should use the initialisation vector I<iv>. The cipher context can be
The initialization vector I<iv> should be a random value. The cipher context
I<ctx> should use the initialisation vector I<iv>. The cipher context can be
set using L<EVP_EncryptInit_ex>. The hmac context can be set using L<HMAC_Init_ex>.
When the client presents a session ticket, the callback function with be called
with I<enc> set to 0 indicating that the I<cb> function should retr
ei
ve a set
with I<enc> set to 0 indicating that the I<cb> function should retr
ie
ve a set
of parameters. In this case I<name> and I<iv> have already been parsed out of
the session ticket. The OpenSSL library expects that the I<name> will be used
to retrieve a cryptographic parameters and that the cryptographic context
I<ctx> will be set with the retr
ei
ved parameters and the initialization vector
I<ctx> will be set with the retr
ie
ved parameters and the initialization vector
I<iv>. using a function like L<EVP_DecryptInit_ex>. The I<hctx> needs to be set
using L<HMAC_Init_ex>.
If the I<name> is still valid but a renewal of the ticket is required the
callback function should return 2. The library will call the callback again
with an argu
e
ment of enc equal to 1 to set the new ticket.
with an argument of enc equal to 1 to set the new ticket.
The return value of the I<cb> function is used by OpenSSL to determine what
further processing will occur. The following return values have meaning:
...
...
@@ -92,7 +92,7 @@ continue on those parameters.
=item Z<>0
This indicates that it was not possible to set/retrieve a session ticket and
the SSL/TLS session will continue by by neg
iotation
ing a set of cryptographic
the SSL/TLS session will continue by by neg
otiat
ing a set of cryptographic
parameters or using the alternate SSL/TLS resumption mechanism, session ids.
If called with enc equal to 0 the library will call the I<cb> again to get
...
...
@@ -107,10 +107,10 @@ This indicates an error.
=head1 NOTES
Session resumption shortcuts the TLS so that the client certificate
neg
iot
ation don't occur. It makes up for this by storing client certificate
neg
oti
ation don't occur. It makes up for this by storing client certificate
an all other negotiated state information encrypted within the ticket. In a
resumed session the applications will have all this state information available
exactly as if a full neg
iotation had occu
red.
exactly as if a full neg
otiation had occur
red.
If an attacker can obtain the key used to encrypt a session ticket, they can
obtain the master secret for any ticket using that key and decrypt any traffic
...
...
@@ -125,7 +125,7 @@ enable an attacker to obtain the session keys.
=head1 EXAMPLES
Reference Implemention:
Reference Implement
at
ion:
SSL_CTX_set_tlsext_ticket_key_cb(SSL,ssl_tlsext_ticket_key_cb);
....
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录