| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| ghostunnel-windows-amd64.exe | 2026-07-26 | 61.2 MB | |
| ghostunnel-darwin-amd64 | 2026-07-26 | 46.9 MB | |
| ghostunnel-darwin-arm64 | 2026-07-26 | 43.6 MB | |
| ghostunnel-darwin-universal | 2026-07-26 | 90.5 MB | |
| ghostunnel-linux-amd64 | 2026-07-26 | 44.5 MB | |
| ghostunnel-linux-arm64 | 2026-07-26 | 41.7 MB | |
| README.md | 2026-07-26 | 1.1 kB | |
| Version 1.11.2 source code.tar.gz | 2026-07-26 | 14.2 MB | |
| Version 1.11.2 source code.zip | 2026-07-26 | 18.7 MB | |
| Totals: 9 Items | 361.3 MB | 0 | |
Bug fix release.
Bug Fixes
- UNIX socket targets in client mode restored. The stricter
--targetvalidation added in v1.11.0 (#762) rejectedunix:PATHtargets in client mode, even though they had worked through v1.10.0 (and remained supported in server mode). Client mode now accepts bothHOST:PORTandunix:PATHtargets again, while the listen-onlysystemd:/launchd:schemes stay rejected at startup. This is useful for sidecar setups where two processes rendezvous on a shared socket instead of a localhost port, with mTLS running over the socket. Note that aunix:PATHtarget carries no hostname, so set--override-server-nameto give hostname verification a name to check (unless--use-workload-apior--verify-spki-pinreplaces hostname verification) (#799, thanks to @molchalih).
Other
- Documentation fixes for
--use-workload-api-timeout. The v1.11.1 release notes and the Linux man page now correctly document the--use-workload-api-timeoutflag introduced in that release, instead of describing the initial SPIFFE Workload API fetch as bounded by the connect timeout (#800).