Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS session ticket caching reworked #15774

Closed
wants to merge 7 commits into from
Closed

Conversation

icing
Copy link
Contributor

@icing icing commented Dec 18, 2024

Described in detail in internal doc TLS-SESSIONS.md

Main points:

  • use a new ssl_peer_key for cache lookups by connection filters
  • recognize differences between TLSv1.3 and other tickets
    • TLSv1.3 tickets are single-use, cache can hold several of them for a peer
    • TLSv1.2 are reused, keep only a single one per peer
  • differentiate between ticket BLOB to store (that could be persisted) and object instances
  • use put/take/return pattern for cache access
  • remember TLS version, ALPN protocol, time received and lifetime of ticket
  • auto-expire tickets after their lifetime

lib/vtls/vtls_scache.c Outdated Show resolved Hide resolved
Described in detail in internal doc TLS-SESSIONS.md

Main points:
- use a new `ssl_peer_key` for cache lookups by connection filters
- recognize differences between TLSv1.3 and other tickets
  * TLSv1.3 tickets are single-use, cache can hold several of them for a peer
  * TLSv1.2 are reused, keep only a single one per peer
- differentiate between ticket BLOB to store (that could be persisted) and object instances
- use put/take/return pattern for cache access
- remember TLS version, ALPN protocol, time received and lifetime of ticket
- auto-expire tickets after their lifetime
lib/llist.c Show resolved Hide resolved
lib/vtls/vtls_scache.c Show resolved Hide resolved
@bagder bagder closed this in fa0ccd9 Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants