Skip to content

Add TLS: tls:// scheme, TlsConfig, upgrade after INFO and handshake - #86

Merged
kafkiansky merged 1 commit into
0.5.xfrom
features/tls
Nov 11, 2026
Merged

kafkiansky merged 1 commit into
0.5.xfrom
features/tls

Conversation

@kafkiansky

Copy link
Copy Markdown
Collaborator

No description provided.

…irst

- Nats\TlsConfig (CA, client certificate and encrypted key, verify peer, server name/SNI,
  handshake first) via Config::$tls, fromArray and the uri (tls:// or tls_* options)
- the connection is upgraded to TLS when the server requires it, even without options;
  TLS required by the client but not offered fails with TlsIsNotAvailable,
  a failed handshake with TlsHandshakeFailed; CONNECT sends tls_required
- Framer reads the socket on demand and reads the startup INFO up to its line end only:
  plain data past INFO before the TLS handshake is refused
- servers discovered by IP verify the certificate against the announcing server's
  DNS name, or their own address when it has none
- the server's -ERR wins over a failed PING write during the handshake
- amphp/socket ^2.4 (withoutPeerNameVerification)
- compose: nats-tls, nats-mtls, nats-tls-first with self-signed test certificates
@kafkiansky kafkiansky self-assigned this Nov 11, 2026
@kafkiansky kafkiansky added the enhancement New feature or request label Nov 11, 2026
@kafkiansky
kafkiansky merged commit ee48b1d into 0.5.x Nov 11, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant