Lines Matching defs:session

203                               const SSL_SESSION *session,
263 master_key_size = SSL_SESSION_get_master_key(session,
493 /* Terminate old session and resume with early data. */
1187 /* Create a session based on SHA-256 */
1326 /* Create a session based on SHA-256 */
2062 /* Set up session cache */
2107 * In TLSv1.3 we should have created a new session even though we have
2149 * This should clear sess2 from the cache because it is a "bad" session.
2188 /* We should have automatically removed the session from the cache */
2263 * Delete the session from the internal cache to force a lookup from
2265 * SSL_CTX_remove_session() also marks the session as non-resumable.
2414 /* We don't need the reference to the session, so free it */
4277 * is associated with each handshake - not the session. Therefore it
4726 /* Create a session based on SHA-256 */
4751 /* Check we can resume a session with a different SHA-256 ciphersuite */
4771 * Check attempting to resume a SHA-256 session with no SHA-256 ciphersuites
4791 /* Create a session based on SHA384 */
4816 * enable us to make some session changes.
4822 /* Trick the client into thinking this session is for a different digest */
4828 * ciphersuite, but client thinks the session is for SHA-256, so it should
5087 * be cached in the session from the original handshake, regardless of what
6075 * For a resumed session we expect to add the ClientHello extension. For the
6973 /* Skip session id */
8080 * We only want sessions to resume from tickets - not the session cache. So
8895 * Test session ordering and timeout
8914 /* assign unique session ids */
9016 * Test that a session cache overflow works as expected
9017 * Test 0: TLSv1.3, timeout on new session later than old session
9018 * Test 1: TLSv1.2, timeout on new session later than old session
9019 * Test 2: TLSv1.3, timeout on new session earlier than old session
9020 * Test 3: TLSv1.2, timeout on new session earlier than old session
9067 * Cause this session to have a longer timeout than the next session to
9084 * Session cache size is 1 and we already populated the cache with a session
9096 * The session we just negotiated may have been already removed from the
9233 * A TLSv1.3 session does not associate a session with a servername,
9234 * but a TLSv1.2 session does.
9252 * session but is now, the server hostname will be empty, but the client
10606 * the same session - and mark the session as not_resuamble at the end
10630 * mark the session as not_resumable.
10682 * TLSv1.3 only uses a session cache if either max_early_data > 0 (used for
10711 * session resumption has already occurred, but before any session
10713 * handshake resuming the same session.
10722 * can cause sessions in the session cache which cannot be deleted.
10754 /* We should never exceed the session cache size limit */