Lines Matching defs:session

592         SSL_SESSION_free(s->session);
593 s->session = NULL;
938 * we can "construct" a session to give us the desired check - i.e. to
939 * find if there's a session in the hash table that would conflict with
940 * any new session built out of this id/id_len and the ssl_version in use
1222 if (s->session != NULL) {
1224 SSL_SESSION_free(s->session);
1610 if ((s == NULL) || (s->session == NULL))
1613 return s->session->peer;
1620 if ((s == NULL) || (s->session == NULL))
1623 r = s->session->peer_chain;
2189 || ((s->session == NULL || s->session->ext.max_early_data == 0)
2448 if (!s->session || SSL_in_init(s) || ossl_statem_get_in_handshake(s))
2450 if (s->session->flags & SSL_SESS_FLAG_EXTMS)
2870 * In TLSv1.3 on the server SNI is not associated with the session
2885 return s->session->ext.hostname;
2894 * attempted and the session from the original handshake had a
2900 * - If the session from the original handshake had a servername accepted
2911 && s->session != NULL
2912 && s->session->ssl_version != TLS1_3_VERSION)
2913 return s->session->ext.hostname;
2915 if (!SSL_IS_TLS13(s) && s->hit && s->session->ext.hostname != NULL)
2916 return s->session->ext.hostname;
3156 if (s->session == NULL
3202 * session with a matching session ID.
3395 * session ticket, and the client will accordingly send us early data
3418 /* By default we send two session tickets automatically in TLSv1.3 */
3466 * Free internal session cache. However: the remove_cb() may reference
3469 * As the ex_data handling routines might also touch the session cache,
3739 * would be rather hard to do anyway :-). Also if the session has already
3742 if (s->session->session_id_length == 0 || s->session->not_resumable)
3747 * associated with this session, so when we try to resume it and
3749 * indication that this is actually a session for the proper application
3754 if (s->server && s->session->sid_ctx_length == 0
3762 * Add the session to the internal cache. In server side TLSv1.3 we
3764 * with only a dummy session id so there is no reason to cache it,
3769 * session timeout events
3779 SSL_CTX_add_session(s->session_ctx, s->session);
3782 * Add the session to the external cache. We do this even in server side
3784 * know about the creation of a session and aren't doing a full cache.
3787 SSL_SESSION_up_ref(s->session);
3788 if (!s->session_ctx->new_session_cb(s, s->session))
3789 SSL_SESSION_free(s->session);
4084 * Otherwise, copy configuration state, and session if set.
4089 if (s->session != NULL) {
4091 * Arranges to share the same session via up_ref. This "copies"
4092 * session-id, SSL_METHOD, sid_ctx, and 'cert'
4098 * No session has been established yet, so we have to expect that
4228 if ((s->session != NULL) && (s->session->cipher != NULL))
4229 return s->session->cipher;
4363 * If the session ID context matches that of the parent SSL_CTX,
4518 size_t SSL_SESSION_get_master_key(const SSL_SESSION *session,
4522 return session->master_key_length;
4523 if (outlen > session->master_key_length)
4524 outlen = session->master_key_length;
4525 memcpy(out, session->master_key, outlen);
4622 if (s == NULL || s->session == NULL)
4624 return s->session->psk_identity_hint;
4629 if (s == NULL || s->session == NULL)
4631 return s->session->psk_identity;
5109 X509 *cert = s->session != NULL ? s->session->peer : NULL;
5227 X509 *cert = s->session != NULL ? s->session->peer : NULL;
5304 * With SSL_VERIFY_NONE the session may be cached and re-used despite a
5311 * session.
5818 if (ssl->session != NULL && USE_MAX_FRAGMENT_LENGTH_EXT(ssl->session))
5819 return GET_MAX_FRAGMENT_LENGTH(ssl->session);
5828 if (ssl->session != NULL && USE_MAX_FRAGMENT_LENGTH_EXT(ssl->session)
5829 && ssl->split_send_fragment > GET_MAX_FRAGMENT_LENGTH(ssl->session))
5830 return GET_MAX_FRAGMENT_LENGTH(ssl->session);