Skip to content

Proxy server should offer both nested TLS and inner-TLS only on different ports#153

Merged
ameba23 merged 11 commits intopeg/use-nested-attested-tlsfrom
peg/nested-tls-and-inner-only
Mar 20, 2026
Merged

Proxy server should offer both nested TLS and inner-TLS only on different ports#153
ameba23 merged 11 commits intopeg/use-nested-attested-tlsfrom
peg/nested-tls-and-inner-only

Conversation

@ameba23
Copy link
Collaborator

@ameba23 ameba23 commented Mar 19, 2026

This make the proxy-server offer both nested and inner-handshake only TLS on different ports.

Instead of only accepting nested TLS, the server now always exposes an inner-only attested TLS listener and can optionally expose the existing outer nested-TLS listener as well.

The server construction API was refactored around OuterTlsConfig / OuterTlsMode, which groups the outer listener bind address with either raw cert/key input or a prebuilt rustls server config. This means we need just one constructor and keeps the outer-session-specific setup in one place.

CLI changes BREAKING:

  • server now takes --outer-listen-addr and --inner-listen-addr instead of --listen-addr
  • attested-file-server also updated similarly

Test coverage was expanded to cover the new behavior:

  • dual-listener address reporting
  • inner-only listener negotiating HTTP/2 by default
  • existing nested client/server behavior still working through the outer listener

@ameba23 ameba23 marked this pull request as draft March 19, 2026 11:18
@ameba23 ameba23 marked this pull request as ready for review March 20, 2026 08:20
@ameba23 ameba23 merged commit be7581a into peg/use-nested-attested-tls Mar 20, 2026
2 checks passed
@ameba23 ameba23 deleted the peg/nested-tls-and-inner-only branch March 20, 2026 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant