Lines Matching refs:session
9 SSL_CTX_decrypt_session_ticket_fn - manage session ticket application data
32 with a session, and placed into a session ticket. Either callback function may
35 B<gen_cb> is the application defined callback invoked when a session ticket is
37 at this time to add application data to the session ticket. The value of B<arg>
41 B<dec_cb> is the application defined callback invoked after session ticket
42 decryption has been attempted and any session ticket application data is
44 the session data. The B<keyname> and B<keyname_len> arguments identify the key
45 used to decrypt the session ticket. The B<status> argument is the result of the
51 B<data> and B<len> into B<ss> which is then placed into any generated session
52 tickets. It can be called at any time before a session ticket is created to
53 update the data placed into the session ticket. However, given that sessions
55 the application that a session ticket is about to be generated.
57 SSL_SESSION_get0_ticket_appdata() assigns B<data> to the session ticket
58 application data and assigns B<len> to the length of the session ticket
60 SSL_SESSION_set1_ticket_appdata() or by a session ticket. NULL will be assigned
61 to B<data> and 0 will be assigned to B<len> if there is no session ticket
63 after a session has been created. The B<dec_cb> is provided to notify the
64 application that a session ticket has just been decrypted.
74 the key that was used to encrypt the session ticket.
93 A ticket was successfully decrypted, any session ticket application data should
147 no session data will be available and the callback must not use the B<ss>
150 SSL_SESSION_get0_ticket_appdata() using the session provided in the B<ss>
156 By default, in TLSv1.2 and below, a new session ticket is not issued on a
