Changelog for 0.10.4:

• Build now uses Go 1.24

Changelog for 0.10.3:

A panic was reported by a user from sshmux after we upgraded to Go 1.23 which handles TLS differently.

This new version fixes the issues and requires the same version on the client and server to work.

Add Google to OAuth options, and GitHub organisations as ACL filter

• --oauth-provider=google is now supported
• For --oauth-provider=github, --oauth-acl can now include an organisation such as org:inlets so that anyone with membership is able to authenticate

For HTTP tunnels, basic auth and/or bearer tokens can now be used with OAuth

See examples at: https://inlets.dev/blog/tutorial/2025/03/10/secure-http-tunnels-with-oauth.html

Changelog for 0.10.0:

Enhancements for inlets-pro http tunnels, with new flags for the client:

• HTTP Header Modification - add/remove request and response headers
• Authenticate HTTPs tunnels - with OAuth, Bearer tokens and Basic Auth

Example from the OAuth page displayed to unauthenticated users:

Changelog for 0.9.40:

Commits

Changes: 0.9.39...0.9.40

Generated by Derek

Changelog for 0.9.39:

All server commands will now take a consistent --proxy-protocol form flag, not a mixture of that and --proxy-proto

Generated by Derek

Changelog for 0.9.38:

inlets-pro sshmux has been renamed to inlets-pro snimux because it can mux TLS, rather than just SSH.

Generated by Derek

Changelog for 0.9.37:

• Enables an allow list for the sshmux command's config file for IP allow lists - using CIDR or plain IP format, run with --help for an example of how to use this
• Fixes reliability for handling of proxy protocol for retrieving client IPs

If your home IP was 35.202.222.154, you could write:

upstreams:
  - name: nuc.example.com
    upstream: 192.168.0.120:22
    allowed:
    - 35.202.222.154

Changes: 0.9.36...0.9.37

Generated by Derek

Changelog for 0.9.36:

Fixes issue in 0.9.35 where proxy protocol source addresses were empty when not running the inlets tcp server behind an LB.

Generated by Derek