v1.5.0

Nowhere 1.5.0

One port. Two transports. Split directions.

Nowhere 1.5 introduces a new wire protocol, independent upload and download carrier selection, and the native Rust Vector SOCKS5 client.

Important

This release is not wire-compatible with earlier Nowhere releases. Portal and clients must be upgraded together. The default ALPN remains now/1, so mixed versions may complete TLS or QUIC negotiation before failing during application authentication.

Highlights

• Serve TLS/TCP and QUIC/UDP on the same Portal port.
• Select TLS/TCP or QUIC/UDP independently for upload and download.
• Relay TCP through TLS lanes or QUIC streams.
• Relay UDP through UoT over TLS/TCP or QUIC DATAGRAM.
• Use the native vector:// client as a local SOCKS5 ingress.
• Support SOCKS5 CONNECT, UDP ASSOCIATE, and optional RFC1929 authentication.
• Keep operational controls including directional rate limits, TLS warm lanes, outbound SOCKS5, certificate reload, EVENT telemetry, and graceful shutdown.

Protocol Updates

• Authentication is bound to each TLS or QUIC connection through the TLS exporter.
• Flow setup uses binary targets, 32-bit flow IDs, and compact result signaling.
• QUIC authentication and the optional first flow share the first bidirectional stream.
• Authentication-pending DATAGRAMs and data sent before flow readiness are discarded.
• QUIC DATAGRAM processing uses direct payload slices and bounded reassembly state.

Configuration

• The legacy spec parameter has been removed.
• Custom ALPN values remain supported and must match on Portal and clients.
• Unknown URL parameters are ignored; the first repeated value wins.
• Vector uses pool only for the tcp/tcp combination, with a default of 5 and a maximum of 256.
• Empty, omitted, or none SNI disables certificate verification. Production deployments should use an explicit DNS name with a CA-trusted certificate.

Upgrade Notes

1. Upgrade Portal and compatible clients together.
2. Remove spec from stored configuration URLs.
3. Confirm the intended ALPN on both sides.
4. Verify one TCP flow and one UDP flow after deployment.

The current Anywhere client still uses the previous wire format and cannot connect to a 1.5 Portal. Keep it paired with a matching older Portal until its coordinated protocol update is available.

Full Changelog: v1.4.0...v1.5.0

v1.4.0

Full Changelog: v1.3.4...v1.4.0

v1.3.4

Full Changelog: v1.3.3...v1.3.4

v1.3.3

Full Changelog: v1.3.2...v1.3.3

v1.3.2

What's Changed

• Improve TCP relay responsiveness by @ohmycggk in #1

New Contributors

• @ohmycggk made their first contribution in #1

Full Changelog: v1.3.1...v1.3.2

v1.3.1

Full Changelog: v1.3.0...v1.3.1

v1.3.0

Full Changelog: v1.2.5...v1.3.0

v1.2.5

Full Changelog: v1.2.4...v1.2.5

v1.2.4

Full Changelog: v1.2.3...v1.2.4

v1.2.3

Full Changelog: https://github.com/NodePassProject/Nowhere/commits/v1.2.3