Skip to content

Releases: inlets/inlets-pro

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

13 Mar 13:55
Compare
Choose a tag to compare

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

Allow basic auth/bearer tokens and OAuth to be combined

11 Mar 12:18
Compare
Choose a tag to compare

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

OAuth and other HTTP middlewares for HTTP tunnels

28 Feb 15:08
Compare
Choose a tag to compare

Changelog for 0.10.0:

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

Example from the OAuth page displayed to unauthenticated users:

Screenshot from OAuth flow

Support LemonSqueezy licensing for TCP/HTTP clients

19 Dec 17:26
Compare
Choose a tag to compare

Changelog for 0.9.40:

Commits

Changes: 0.9.39...0.9.40

Generated by Derek

Rename proxy-proto to proxy-protocol for consistency

28 Oct 13:05
Compare
Choose a tag to compare

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

Rename sshmux to snimux

28 Oct 11:14
Compare
Choose a tag to compare

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

IP allow lists for sshmux and fixes to proxy protocol for sshmux

11 Oct 15:23
Compare
Choose a tag to compare

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

Fix for proxy protocol header when not running behind lb

08 Oct 10:13
Compare
Choose a tag to compare

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

Proxy Protocol support for inlets uplink data plane

01 Oct 14:19
Compare
Choose a tag to compare

Changelog for 0.9.35:

Commits

Changes: 0.9.34...0.9.35

Generated by Derek

Proxy Protocol support for data plane behind a load-balancer

01 Oct 09:59
Compare
Choose a tag to compare

Proxy Protocol support for data plane behind a load-balancer

The --lb-proxy-protocol flag can be used behind a cloud load-balancer, HAProxy, or similar to receive a real client IP, this works for the data-plane ports on a tcp tunnel server.