Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
OpenHarmony
Third Party Openssl
提交
d93eb21c
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,发现更多精彩内容 >>
提交
d93eb21c
编写于
8月 20, 2001
作者:
L
Lutz Jänicke
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
More interdependencies with respect to shutdown behaviour.
上级
a403188f
变更
4
隐藏空白更改
内联
并排
Showing
4 changed file
with
35 addition
and
9 deletion
+35
-9
doc/ssl/SSL_read.pod
doc/ssl/SSL_read.pod
+13
-3
doc/ssl/SSL_set_shutdown.pod
doc/ssl/SSL_set_shutdown.pod
+4
-1
doc/ssl/SSL_shutdown.pod
doc/ssl/SSL_shutdown.pod
+6
-3
doc/ssl/SSL_write.pod
doc/ssl/SSL_write.pod
+12
-2
未找到文件。
doc/ssl/SSL_read.pod
浏览文件 @
d93eb21c
...
...
@@ -83,9 +83,18 @@ bytes actually read from the TLS/SSL connection.
=item 0
The read operation was not successful, probably because no data was
available. Call SSL_get_error() with the return value B<ret> to find out,
whether an error occurred.
The read operation was not successful, the SSL connection was closed by the
peer by sending a "close notify" alert. The SSL_RECEIVED_SHUTDOWN flag in
the ssl shutdown state is set (see L<SSL_shutdown(3)|SSL_shutdown(3)>,
L<SSL_set_shutdown(3)|SSL_set_shutdown(3)>).
Call SSL_get_error() with the return value B<ret> to find out,
whether an error occurred or the connection was shut down cleanly
(SSL_ERROR_ZERO_RETURN).
SSLv2 (deprecated) does not support a shutdown alert protocol, so it can
only be detected, whether the underlying connection was closed. It cannot
be checked, whether the closure was initiated by the peer or by something
else.
=item E<lt>0
...
...
@@ -101,6 +110,7 @@ L<SSL_get_error(3)|SSL_get_error(3)>, L<SSL_write(3)|SSL_write(3)>,
L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)>, L<SSL_CTX_new(3)|SSL_CTX_new(3)>,
L<SSL_connect(3)|SSL_connect(3)>, L<SSL_accept(3)|SSL_accept(3)>
L<SSL_set_connect_state(3)|SSL_set_connect_state(3)>,
L<SSL_shutdown(3)|SSL_shutdown(3)>, L<SSL_set_shutdown(3)|SSL_set_shutdown(3)>,
L<ssl(3)|ssl(3)>, L<bio(3)|bio(3)>
=cut
doc/ssl/SSL_set_shutdown.pod
浏览文件 @
d93eb21c
...
...
@@ -46,7 +46,10 @@ The shutdown state of the connection is used to determine the state of
the ssl session. If the session is still open, when
L<SSL_clear(3)|SSL_clear(3)> or L<SSL_free(3)|SSL_free(3)> is called,
it is considered bad and removed according to RFC2246.
The actual condition for a correctly closed session is SSL_SENT_SHUTDOWN.
The actual condition for a correctly closed session is SSL_SENT_SHUTDOWN
(according to the TLS RFC, it is acceptable to only send the "close notify"
alert but to not wait for the peer's answer, when the underlying connection
is closed).
SSL_set_shutdown() can be used to set this state without sending a
close alert to the peer (see L<SSL_shutdown(3)|SSL_shutdown(3)>).
...
...
doc/ssl/SSL_shutdown.pod
浏览文件 @
d93eb21c
...
...
@@ -49,9 +49,12 @@ shutdown alert. On success, the second call to SSL_shutdown() will return
with 1.
=item If the peer already sent the "close notify" alert B<and> it was
already processed implicitly inside another call of e.g.
B<SSL_read(3)|SSL_read(3)>, SSL_shutdown() will send the "close notify"
alert, set the SSL_SENT_SHUTDOWN flag and will immediately return with 1.
already processed implicitly inside another function
(L<SSL_read(3)|SSL_read(3)>), the SSL_RECEIVED_SHUTDOWN flag is set.
SSL_shutdown() will send the "close notify" alert, set the SSL_SENT_SHUTDOWN
flag and will immediately return with 1.
Whether SSL_RECEIVED_SHUTDOWN is already set can be checked using the
SSL_get_shutdown() (see also L<SSL_set_shutdown(3)|SSL_set_shutdown(3)> call.
=back
...
...
doc/ssl/SSL_write.pod
浏览文件 @
d93eb21c
...
...
@@ -78,8 +78,18 @@ bytes actually written to the TLS/SSL connection.
=item 0
The write operation was not successful. Call SSL_get_error() with the return
value B<ret> to find out, whether an error occurred.
The write operation was not successful, because the write side of the
SSL connection was shut down (the SSL_SENT_SHUTDOWN flag in the shutdown
state is set) by calling L<SSL_shutdown(3)|SSL_shutdown(3)> or
L<SSL_set_shutdown(3)|SSL_set_shutdown(3)>. It is also possible, that the
underlying connection was closed.
Call SSL_get_error() with the return value B<ret> to find out,
whether an error occurred or the connection was shut down cleanly
(SSL_ERROR_ZERO_RETURN).
SSLv2 (deprecated) does not support a shutdown alert protocol, so it can
only be detected, whether the underlying connection was closed. It cannot
be checked, why the closure happened.
=item E<lt>0
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录