SSL_set_shutdown.pod revision 76866 
1=pod
2
3=head1 NAME
4
5SSL_set_shutdown, SSL_get_shutdown - manipulate shutdown state of an SSL connection
6
7=head1 SYNOPSIS
8
9 #include <openssl/ssl.h>
10
11 void SSL_set_shutdown(SSL *ssl, int mode);
12
13 int SSL_get_shutdown(SSL *ssl);
14
15=head1 DESCRIPTION
16
17SSL_set_shutdown() sets the shutdown state of B<ssl> to B<mode>.
18
19SSL_get_shutdown() returns the shutdown mode of B<ssl>.
20
21=head1 NOTES
22
23The shutdown state of an ssl connection is a bitmask of:
24
25=over 4
26
27=item 0
28
29No shutdown setting, yet.
30
31=item SSL_SENT_SHUTDOWN
32
33A "close notify" shutdown alert was sent to the peer, the connection is being
34considered closed and the session is closed and correct.
35
36=item SSL_RECEIVED_SHUTDOWN
37
38A shutdown alert was received form the peer, either a normal "close notify"
39or a fatal error.
40
41=back
42
43SSL_SENT_SHUTDOWN and SSL_RECEIVED_SHUTDOWN can be set at the same time.
44
45The shutdown state of the connection is used to determine the state of
46the ssl session. If the session is still open, when
47L<SSL_clear(3)|SSL_clear(3)> or L<SSL_free(3)|SSL_free(3)> is called,
48it is considered bad and removed according to RFC2246.
49The actual condition for a correctly closed session is SSL_SENT_SHUTDOWN.
50SSL_set_shutdown() can be used to set this state without sending a
51close alert to the peer (see L<SSL_shutdown(3)|SSL_shutdown(3)>).
52
53If a "close notify" was received, SSL_RECEIVED_SHUTDOWN will be set,
54for setting SSL_SENT_SHUTDOWN the application must however still call
55L<SSL_shutdown(3)|SSL_shutdown(3)> or SSL_set_shutdown() itself.
56
57=head1 RETURN VALUES
58
59SSL_set_shutdown() does not return diagnostic information.
60
61SSL_get_shutdown() returns the current setting.
62
63=head1 SEE ALSO
64
65L<ssl(3)|ssl(3)>, L<SSL_shutdown(3)|SSL_shutdown(3)>,
66L<SSL_clear(3)|SSL_clear(3)>, L<SSL_free(3)|SSL_free(3)>
67
68=cut
69