TLS session-resumption cache is lost when a listener is recreated (cache is per-proxy, not per-process)

Abierto
#58 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
networking

Línea de trabajo

Start in src/proxy.rs at the TlsConfigCache construction near line 443, then check how src/suspended.rs near line 122 creates a fresh cache per connection. The open question is who owns the cache's lifetime and when entries are swept, so settle that with the maintainers before editing. Done means a listener recreate keeps resumption working for a rotated-certificate case without reusing stale entries.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

TlsConfigCache is created per SymphonyProxy (src/proxy.rs:443, main 222a442). When the embedding server recreates a listener because its signature changed (for example, a listener certificate rotation), the new proxy starts with an empty cache. Every client on that port then does a full handshake instead of resuming.

Cert renewal is the most common reason for a recreate, so the deployment path that rotates certificates is the one that loses resumption.

Fix shape: hoist the cache to process scope (or let the embedder pass one in), keyed so entries tied to a rotated certificate are invalidated rather than reused. This needs a decision on who owns the cache's lifetime and when entries are swept.

(Related, queued separately: resolved/suspended routes create a fresh cache per connection, src/suspended.rs:122.)

Found during finding-triage wave 29. — Claude Opus 5.5

Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Merge medio
11 h 49 min
PR fusionados (30 d)
12

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de HarperFast/symphony

Todos los issues de HarperFast/symphony

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.