Botan 3.8.1
Crypto and TLS for C&
Botan::TLS::Session_Manager_Noop Class Referencefinal

#include <tls_session_manager_noop.h>

Inheritance diagram for Botan::TLS::Session_Manager_Noop:
Botan::TLS::Session_Manager

Public Member Functions

virtual std::optional< std::pair< Session, uint16_t > > choose_from_offered_tickets (const std::vector< PskIdentity > &tickets, std::string_view hash_function, Callbacks &callbacks, const Policy &policy)
 
virtual bool emits_session_tickets ()
 
std::optional< Session_Handleestablish (const Session &, const std::optional< Session_ID > &=std::nullopt, bool=false) override
 Save a new Session and assign a Session_Handle (TLS Server)
 
virtual std::vector< Session_with_Handlefind (const Server_Information &info, Callbacks &callbacks, const Policy &policy)
 Find all sessions that match a given server info.
 
size_t remove (const Session_Handle &) override
 
size_t remove_all () override
 
virtual std::optional< Sessionretrieve (const Session_Handle &handle, Callbacks &callbacks, const Policy &policy)
 Retrieves a specific session given a handle.
 
 Session_Manager_Noop ()
 
void store (const Session &, const Session_Handle &) override
 Save a Session under a Session_Handle (TLS Client)
 

Protected Member Functions

std::vector< Session_with_Handlefind_some (const Server_Information &, const size_t) override
 Internal retrieval function to find sessions to resume.
 
recursive_mutex_typemutex ()
 
std::optional< Sessionretrieve_one (const Session_Handle &) override
 Internal retrieval function for a single session.
 

Protected Attributes

std::shared_ptr< RandomNumberGeneratorm_rng
 

Detailed Description

An implementation of Session_Manager that does not save sessions at all, preventing session resumption.

For applications that do not want to support session resumption at all, this is typically a good choice.

Definition at line 23 of file tls_session_manager_noop.h.

Constructor & Destructor Documentation

◆ Session_Manager_Noop()

Botan::TLS::Session_Manager_Noop::Session_Manager_Noop ( )

Definition at line 15 of file tls_session_manager_noop.cpp.

15: Session_Manager(std::make_shared<Null_RNG>()) {}
Session_Manager(const std::shared_ptr< RandomNumberGenerator > &rng)

References Botan::TLS::Session_Manager::Session_Manager().

Member Function Documentation

◆ choose_from_offered_tickets()

std::optional< std::pair< Session, uint16_t > > Botan::TLS::Session_Manager::choose_from_offered_tickets ( const std::vector< PskIdentity > & tickets,
std::string_view hash_function,
Callbacks & callbacks,
const Policy & policy )
virtualinherited

Lets the server application choose a PSK to use for a new TLS connection. Implementers must make sure that the PSK's associated hash function is equal to the passed hash_function.

RFC 8446 4.2.11 The server MUST ensure that it selects a compatible PSK (if any) and cipher suite.

The default implementation simply tries to retrieve all tickets in the order offered by the peer and picks the first that is found and features a matching hash algorithm.

This method is called only by TLS 1.3 servers.

Parameters
ticketsa list of tickets that were offered by the client
hash_functionthe hash algorithm name we are going to use for the to-be-negotiated connection
callbackscallbacks to be used for session policy decisions
policypolicy to be used for session policy decisions
Returns
a std::pair of the Session associated to the choosen PSK and the index of the selected ticket; std::nullopt if no PSK was chosen for usage (will result in a full handshake)
Note
if no PSK is chosen, the server will attempt a regular handshake.

Definition at line 202 of file tls_session_manager.cpp.

206 {
207 // Note that the TLS server currently does not ensure that tickets aren't
208 // reused. As a result, no locking is required on this level.
209
210 for(uint16_t i = 0; const auto& ticket : tickets) {
211 auto session = retrieve(Opaque_Session_Handle(ticket.identity()), callbacks, policy);
212 if(session.has_value() && session->ciphersuite().prf_algo() == hash_function &&
213 session->version().is_tls_13_or_later()) {
214 return std::pair{std::move(session.value()), i};
215 }
216
217 // RFC 8446 4.2.10
218 // For PSKs provisioned via NewSessionTicket, a server MUST validate
219 // that the ticket age for the selected PSK identity [...] is within a
220 // small tolerance of the time since the ticket was issued. If it is
221 // not, the server SHOULD proceed with the handshake but reject 0-RTT,
222 // and SHOULD NOT take any other action that assumes that this
223 // ClientHello is fresh.
224 //
225 // TODO: The ticket-age is currently not checked (as 0-RTT is not
226 // implemented) and we simply take the SHOULD at face value.
227 // Instead we could add a policy check letting the user decide.
228
229 ++i;
230 }
231
232 return std::nullopt;
233}
virtual std::optional< Session > retrieve(const Session_Handle &handle, Callbacks &callbacks, const Policy &policy)
Retrieves a specific session given a handle.
Strong< std::vector< uint8_t >, struct Opaque_Session_Handle_ > Opaque_Session_Handle
holds an opaque session handle as used in TLS 1.3 that could be either a ticket for stateless resumpt...
Definition tls_session.h:38

References retrieve().

Referenced by Botan::TLS::PSK::select_offered_psk(), and store().

◆ emits_session_tickets()

virtual bool Botan::TLS::Session_Manager::emits_session_tickets ( )
inlinevirtualinherited

Declares whether the given Session_Manager implementation may emit session tickets. Note that this does not mean that the implementation must always emit tickets.

Concrete implementations should declare this, to allow the TLS implementations to act accordingly. E.g. to advertise support for session tickets in their Server Hello.

Returns
true if the Session_Manager produces session tickets

Reimplemented in Botan::TLS::Session_Manager_Hybrid, Botan::TLS::Session_Manager_In_Memory, Botan::TLS::Session_Manager_SQL, and Botan::TLS::Session_Manager_Stateless.

Definition at line 214 of file tls_session_manager.h.

214{ return false; }

◆ establish()

std::optional< Session_Handle > Botan::TLS::Session_Manager_Noop::establish ( const Session & session,
const std::optional< Session_ID > & id = std::nullopt,
bool tls12_no_ticket = false )
inlineoverridevirtual

Save a new Session and assign a Session_Handle (TLS Server)

Save a new session on a best effort basis; the manager may not in fact be able to save the session for whatever reason; this is not an error. Callers cannot assume that calling establish() followed immediately by retrieve() or choose_from_offered_tickets() will result in a successful lookup. In case no session was stored, std::nullopt is returned.

This method is only called on TLS servers.

Note that implementations will silently refrain from sending session tickets to the client when this method returns std::nullopt.

Parameters
sessionto save
idto use (instead of an ID chosen by the manager)
tls12_no_ticketdisable tickets for this establishment (set when TLS 1.2 client does not support them)
Returns
a Session_Handle containing either an ID or a ticket if the session was saved, otherwise std::nullopt

Reimplemented from Botan::TLS::Session_Manager.

Definition at line 27 of file tls_session_manager_noop.h.

29 {
30 return std::nullopt;
31 }

◆ find()

std::vector< Session_with_Handle > Botan::TLS::Session_Manager::find ( const Server_Information & info,
Callbacks & callbacks,
const Policy & policy )
virtualinherited

Find all sessions that match a given server info.

TLS clients use this to obtain session resumption information for a server they are wishing to handshake with. Typically, session info will have been received in prior connections to that same server and stored using Session_Manager::store().

The default implementation will invoke Session_Manager::find_some() and filter the result against a policy. Most notably an expiry check. Expired sessions will be removed via Session_Manager::remove().

The TLS client implementations will query the session manager exactly once per handshake attempt. If no reuse is desired, the session manager may remove the sessions internally when handing them out to the client. The default implementation adheres to Policy::reuse_session_tickets().

For TLS 1.2 the client implementation will attempt a resumption with the first session in the returned list. For TLS 1.3, it will offer all found sessions to the server.

Applications that wish to implement their own Session_Manager may override the default implementation to add further policy checks. Though, typically implementing Session_Manager::find_some() and relying on the default implementation is enough.

Parameters
infothe info about the server we want to handshake with
callbackscallbacks to be used for session policy decisions
policypolicy to be used for session policy decisions
Returns
a list of usable sessions that might be empty if no such session exists or passed the policy validation

Reimplemented in Botan::TLS::Session_Manager_Hybrid.

Definition at line 157 of file tls_session_manager.cpp.

159 {
160 auto allow_reusing_tickets = policy.reuse_session_tickets();
161
162 // Session_Manager::find() must be an atomic getter if ticket reuse is not
163 // allowed. I.e. each ticket handed to concurrently requesting threads must
164 // be unique. In that case we must hold a lock while retrieving a ticket.
165 // Otherwise, no locking is required on this level.
166 std::optional<lock_guard_type<recursive_mutex_type>> lk;
167 if(!allow_reusing_tickets) {
168 lk.emplace(mutex());
169 }
170
171 auto sessions_and_handles = find_and_filter(info, callbacks, policy);
172
173 // std::vector::resize() cannot be used as the vector's members aren't
174 // default constructible.
175 const auto session_limit = policy.maximum_session_tickets_per_client_hello();
176 while(session_limit > 0 && sessions_and_handles.size() > session_limit) {
177 sessions_and_handles.pop_back();
178 }
179
180 // RFC 8446 Appendix C.4
181 // Clients SHOULD NOT reuse a ticket for multiple connections. Reuse of
182 // a ticket allows passive observers to correlate different connections.
183 //
184 // When reuse of session tickets is not allowed, remove all tickets to be
185 // returned from the implementation's internal storage.
186 if(!allow_reusing_tickets) {
187 // The lock must be held here, otherwise we cannot guarantee the
188 // transactional retrieval of tickets to concurrently requesting clients.
189 BOTAN_ASSERT_NOMSG(lk.has_value());
190 for(const auto& [session, handle] : sessions_and_handles) {
191 if(!session.version().is_pre_tls_13() || !handle.is_id()) {
192 remove(handle);
193 }
194 }
195 }
196
197 return sessions_and_handles;
198}
#define BOTAN_ASSERT_NOMSG(expr)
Definition assert.h:61
virtual size_t remove(const Session_Handle &handle)=0
recursive_mutex_type & mutex()

References BOTAN_ASSERT_NOMSG, Botan::TLS::Policy::maximum_session_tickets_per_client_hello(), mutex(), remove(), and Botan::TLS::Policy::reuse_session_tickets().

Referenced by store().

◆ find_some()

std::vector< Session_with_Handle > Botan::TLS::Session_Manager_Noop::find_some ( const Server_Information & info,
const size_t max_sessions_hint )
inlineoverrideprotectedvirtual

Internal retrieval function to find sessions to resume.

Try to find saved sessions using info about the server we're planning to connect to. It should return a list of sessions in preference order of the session manager.

Applications that wish to implement their own Session_Manager will have to provide an implementation for it.

Note that the TLS client implementations do not perform any checks on the validity of the session for a given info. Particularly, it is the Session_Manager's responsibility to ensure the restrictions posed in RFC 8446 4.6.1 regarding server certificate validity for the given info.

This is called for TLS clients only.

Parameters
infothe information about the server
max_sessions_hinta non-binding guideline for an upper bound of sessions to return from this method (will be at least 1 but potentially more)
Returns
the found sessions along with their handles (containing either a session ID or a ticket)

Implements Botan::TLS::Session_Manager.

Definition at line 42 of file tls_session_manager_noop.h.

42{ return {}; }

◆ mutex()

◆ remove()

size_t Botan::TLS::Session_Manager_Noop::remove ( const Session_Handle & handle)
inlineoverridevirtual

Remove a specific session from the cache, if it exists. The handle might contain either a session ID or a ticket.

Parameters
handlea Session_Handle of the session to be removed
Returns
the number of sessions that were removed

Implements Botan::TLS::Session_Manager.

Definition at line 35 of file tls_session_manager_noop.h.

35{ return 0; }

◆ remove_all()

size_t Botan::TLS::Session_Manager_Noop::remove_all ( )
inlineoverridevirtual

Remove all sessions from the cache

Returns
the number of sessions that were removed

Implements Botan::TLS::Session_Manager.

Definition at line 37 of file tls_session_manager_noop.h.

37{ return 0; }

◆ retrieve()

std::optional< Session > Botan::TLS::Session_Manager::retrieve ( const Session_Handle & handle,
Callbacks & callbacks,
const Policy & policy )
virtualinherited

Retrieves a specific session given a handle.

This is typically used by TLS servers to obtain resumption information for a previous call to Session_Manager::establish() when a client requested resumption using the handle.

Even if the session is found successfully, it is returned only if it passes policy validations. Most notably an expiry check. If the expiry check fails, the default implementation calls Session_Manager::remove() for the provided handle.

Applications that wish to implement their own Session_Manager may override the default implementation to add further policy checks. Though, typically implementing Session_Manager::retrieve_one() and relying on the default implementation is enough.

Parameters
handlethe Session_Handle to be retrieved
callbackscallbacks to be used for session policy decisions
policypolicy to be used for session policy decisions
Returns
the obtained session or std::nullopt if no session was found or the policy checks failed

Reimplemented in Botan::TLS::Session_Manager_Hybrid.

Definition at line 38 of file tls_session_manager.cpp.

40 {
41 // Retrieving a session for a given handle does not require locking on this
42 // level. Concurrent threads might handle the removal of an expired ticket
43 // more than once, but removing an already removed ticket is a harmless NOOP.
44
45 auto session = retrieve_one(handle);
46 if(!session.has_value()) {
47 return std::nullopt;
48 }
49
50 // A value of '0' means: No policy restrictions.
51 const std::chrono::seconds policy_lifetime =
52 (policy.session_ticket_lifetime().count() > 0) ? policy.session_ticket_lifetime() : std::chrono::seconds::max();
53
54 // RFC 5077 3.3 -- "Old Session Tickets"
55 // A server MAY treat a ticket as valid for a shorter or longer period of
56 // time than what is stated in the ticket_lifetime_hint.
57 //
58 // RFC 5246 F.1.4 -- TLS 1.2
59 // If either party suspects that the session may have been compromised, or
60 // that certificates may have expired or been revoked, it should force a
61 // full handshake. An upper limit of 24 hours is suggested for session ID
62 // lifetimes.
63 //
64 // RFC 8446 4.6.1 -- TLS 1.3
65 // A server MAY treat a ticket as valid for a shorter period of time than
66 // what is stated in the ticket_lifetime.
67 //
68 // Note: This disregards what is stored in the session (e.g. "lifetime_hint")
69 // and only takes the local policy into account. The lifetime stored in
70 // the sessions was taken from the same policy anyways and changes by
71 // the application should have an immediate effect.
72 const auto ticket_age =
73 std::chrono::duration_cast<std::chrono::seconds>(callbacks.tls_current_timestamp() - session->start_time());
74 const bool expired = ticket_age > policy_lifetime;
75
76 if(expired) {
77 remove(handle);
78 return std::nullopt;
79 } else {
80 return session;
81 }
82}
virtual std::optional< Session > retrieve_one(const Session_Handle &handle)=0
Internal retrieval function for a single session.

References remove(), retrieve_one(), Botan::TLS::Policy::session_ticket_lifetime(), and Botan::TLS::Callbacks::tls_current_timestamp().

Referenced by choose_from_offered_tickets(), and store().

◆ retrieve_one()

std::optional< Session > Botan::TLS::Session_Manager_Noop::retrieve_one ( const Session_Handle & handle)
inlineoverrideprotectedvirtual

Internal retrieval function for a single session.

Try to obtain a Session from a Session_Handle that contains either a session ID or a session ticket. This method should not apply any policy decision (such as ticket expiry) but simply be a storage interface.

Applications that wish to implement their own Session_Manager will have to provide an implementation for it.

This method is called only by servers.

Parameters
handlea Session_Handle containing either an ID or a ticket
Returns
the obtained session or std::nullopt if none can be obtained

Implements Botan::TLS::Session_Manager.

Definition at line 40 of file tls_session_manager_noop.h.

40{ return std::nullopt; }

◆ store()

void Botan::TLS::Session_Manager_Noop::store ( const Session & session,
const Session_Handle & handle )
inlineoverridevirtual

Save a Session under a Session_Handle (TLS Client)

Save a session on a best effort basis; the manager may not in fact be able to save the session for whatever reason; this is not an error. Callers cannot assume that calling store() followed immediately by find() will result in a successful lookup.

In contrast to establish(), this stores sessions that were created by the server along with a Session_Handle also coined by the server.

This method is only called on TLS clients.

Parameters
sessionto save
handlea Session_Handle on which this session shoud by stored

Implements Botan::TLS::Session_Manager.

Definition at line 33 of file tls_session_manager_noop.h.

33{}

Member Data Documentation

◆ m_rng


The documentation for this class was generated from the following files: