- Ultra lightweight and fast
- Local, remote and dynamic (SOCKS5) port forwarding
- Works with SSH config and
ssh-agent - Supports Unix sockets
- Automatic re-connection and keep-alives
- Human-friendly TOML configuration
- Cross platform support
- Smart shell completions
Usage:
boring list, l [-g <group>] List all tunnels
boring open, o (-a | -g <group> | <patterns>...)
<patterns>... Open tunnels matching any glob pattern
-a, --all Open all tunnels
-g, --group <group> Open all tunnels in a group
boring close, c Close tunnels (same options as 'open')
boring edit, e Edit the configuration file
boring version, v Show the version number
boring help, h Show this help message
By default, boring reads its configuration from ~/.boring.toml on macOS and Windows, and from $XDG_CONFIG_HOME/boring/.boring.toml on Linux. If $XDG_CONFIG_HOME is not set, it defaults to ~/.config. The location of the config file can be overriden by setting $BORING_CONFIG. The config is a simple TOML file describing your tunnels:
# simple tunnel
[[tunnels]]
name = "dev"
local = "9000"
remote = "localhost:9000"
host = "dev-server" # automatically matches host against SSH config
# example of an explicit host (no SSH config)
[[tunnels]]
name = "prod"
local = "5001"
remote = "localhost:5001"
host = "prod.example.com"
user = "root"
identity = "~/.ssh/id_prod" # will try default ones if not set
# ... more tunnelsCurrently, supported options at tunnel level are:
| Option | Description |
|---|---|
name |
Alias for the tunnel. Required. |
local |
Local address. Can be a "$host:$port" network address or a Unix socket. Can be abbreviated as "$port" in local and socks modes. Required in local, remote and socks modes. |
remote |
Remote address. As above, but can be abbreviated in remote and socks-remote modes. Required in local, remote and socks-remote modes. |
host |
Either a host alias that matches SSH configs or the actual hostname. Required. |
mode |
Mode of the tunnel. Can be either "local", "remote", "socks" or "socks-remote". Default is "local". |
user |
SSH user. If not set, tries to read it from SSH config, defaulting to $USER. |
identity |
SSH identity file. If not set, tries to read it from SSH config and ssh-agent, defaulting to standard identity files. |
port |
SSH port. If not set, tries to read it from SSH config, defaulting to 22. |
group |
Group that the tunnel is assigned to. Groups are only shown in list view if at least one tunnel has a group assigned. Can be used for grouped open, close, and list. |
backend = "openssh" opts a TCP mode = "socks" tunnel into system OpenSSH
on macOS or Linux (/usr/bin/ssh on macOS, ssh from PATH on Linux). Omit it (or use "go") for the existing Go backend.
OpenSSH reads BORING_SSH_CONFIG via -F, including ProxyJump,
SecurityKeyProvider, and AddKeysToAgent. It owns authentication and SOCKS;
boring manages startup, shutdown, and reconnection. No new dependencies are required.
For agent-independent Secure Enclave authentication on macOS, set
IdentityAgent none and AddKeysToAgent no for both the destination and jump
hosts, alongside the existing IdentityFile and SecurityKeyProvider.
OpenSSH needs an unlocked, accessible key; boring does not relay terminal prompts.
Startup times out after 60 seconds. Unknown host keys must be trusted beforehand.
Each tunnel uses its own control socket; ControlMaster, ControlPersist,
ForkAfterAuthentication, and PermitLocalCommand are overridden to keep its
process lifecycle under boring's control. Other forwarding modes and Windows
are not supported by this backend.
Options that can be provided at global and tunnel level (tunnel level takes precedence):
| Option | Description |
|---|---|
keep_alive |
Keep-alive interval in seconds. Default: 120 (2 minutes). |
You can influence the behavior of boring via a couple of environment variables:
Show
| Variable | Description | Default |
|---|---|---|
$BORING_CONFIG |
Config file location | ~/.boring.toml (Mac & Windows) and $XDG_CONFIG_HOME/boring/.boring.toml(Linux) |
$BORING_LOG_FILE |
Log file location | /tmp/boringd.log |
$BORING_SOCK |
Socket location | /tmp/boringd.sock |
$DEBUG |
Enable verbose logging | |
Releases include versioned archives
and SHA256SUMS. Pushing a v* tag runs tests on macOS arm64 and Linux amd64/arm64,
then builds and publishes all four targets. Tags containing - are prereleases.
Linux binaries use CGO_ENABLED=0; the OpenSSH backend still needs ssh in PATH.
| Nix system | Archive target |
|---|---|
aarch64-darwin |
darwin-arm64 |
x86_64-darwin |
darwin-amd64 |
x86_64-linux |
linux-amd64 |
aarch64-linux |
linux-arm64 |
Download URL: https://github.com/ajchemist/boring/releases/download/<tag>/boring-<tag>-<target>.tar.gz.
Each archive contains boring and LICENSE. Pin both the tag and archive SHA-256
in Nix; keep the existing BORING_SSH_CONFIG wrapper. On Linux, add OpenSSH to the
wrapper's PATH. On macOS the backend uses Apple's /usr/bin/ssh directly.
Restart the existing boring daemon when switching binaries.
brew install boringGet one of the pre-built binaries from the releases page. Then move the binary to a location in your $PATH.
git clone https://github.com/alebeck/boring && cd boring
makeThen move the binary in dist to a location in your $PATH.
Note for Windows users
Windows is fully supported since release 0.6.0. Users currently have to build from source, which is very easy. Make sure Go >= 1.25 is installed and then compile viagit clone https://github.com/alebeck/boring && cd boring
.\build_win.batThen, move the executable to a location in your %PATH%.
Shell completion scripts are available for bash, zsh, and fish.
If boring was installed via Homebrew, and you have Homebrew completions enabled, nothing needs to be done.
Otherwise, install completions by adding the following to your shell's config file:
eval "$(boring --shell bash)"source <(boring --shell zsh)boring --shell fish | source- pkg.go.dev: https://pkg.go.dev/github.com/alebeck/boring
- Coveralls: https://coveralls.io/github/alebeck/boring?branch=main
Go gopher logo by Renee French.

