Lines Matching refs:session
5 …e_cb, SSL_CTX_sess_get_get_cb - provide callback functions for server side external session caching
32 called whenever a new session was negotiated.
35 called whenever a session is removed by the SSL engine. For example,
36 this can occur because a session is considered faulty or has become obsolete
40 whenever a TLS client proposed to resume a session but the session
41 could not be found in the internal session cache (see
52 In order to allow external session caching, synchronization with the internal
53 session cache is realized via callback functions. Inside these callback
54 functions, session can be saved to disk or put into a database using the
57 The new_session_cb() is called whenever a new session has been negotiated and
58 session caching is enabled (see L<SSL_CTX_set_session_cache_mode(3)>). The
60 ssl session B<sess>.
62 session is incremented before the callback, on behalf of the application. If
63 the callback returns B<0>, the session will be immediately removed from the
66 application-maintained "external session cache"), and is responsible for
67 calling SSL_SESSION_free() when the session reference is no longer in use.
70 handshake has completed. The server decides when to send the client the session
80 L<SSL_CTX_remove_session(3)> after a session has been used.
82 The remove_session_cb() is called whenever the SSL engine removes a session
83 from the internal cache. This can happen when the session is removed because
85 for all sessions in the internal session cache when
87 the B<ctx> and the ssl session B<sess>. It does not provide any feedback.
90 the session id
92 session caching was disabled. The get_session_cb() is passed the
93 B<ssl> connection and the session id of length B<length> at the memory location
98 is incremented and the session must be explicitly freed with
