Lines Matching refs:ticket
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
43 available. If ticket decryption was successful then the B<ss> argument contains
45 used to decrypt the session ticket. The B<status> argument is the result of the
46 ticket decryption. See the L</NOTES> section below for further details. The value
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
64 application that a session ticket has just been decrypted.
69 assigned to the SSL B<s>. The B<status> indicates the result of the ticket
71 action, as it is called even if ticket decryption fails.
74 the key that was used to encrypt the session ticket.
82 Empty ticket present. No ticket data will be used and a new ticket should be
84 valid for a client to send an empty ticket.
88 The ticket couldn't be decrypted. No ticket data will be used and a new ticket
93 A ticket was successfully decrypted, any session ticket application data should
94 be available. A new ticket should not be sent to the client.
98 Same as B<SSL_TICKET_SUCCESS>, but a new ticket should be sent to the client.
109 policy. Note that in TLSv1.3 a client may send more than one ticket in a single
110 handshake. Therefore, just because one ticket is unacceptable it does not mean
115 Do not use a ticket (if one was available). Do not send a renewed ticket to the
120 Do not use a ticket (if one was available). Send a renewed ticket to the client.
122 If the callback does not wish to change the default ticket behaviour then it
128 Use the ticket. Do not send a renewed ticket to the client. It is an error for
132 If the callback does not wish to change the default ticket behaviour then it
137 Use the ticket. Send a renewed ticket to the client. It is an error for the
141 If the callback does not wish to change the default ticket behaviour then it
156 By default, in TLSv1.2 and below, a new session ticket is not issued on a
158 default behaviour is to always issue a new ticket on resumption. In both cases
159 this behaviour can be changed if a ticket key callback is in use (see
