| hussh(1) | General Commands Manual | hussh(1) |
NAME
hussh - Memory-safe SSH daemon for restricted TCP forwarding
SYNOPSIS
hussh [options]
DESCRIPTION
hussh is a minimal SSH server that only implements TCP forwarding ("direct-tcpip"). It is intended for use as a restricted SSH tunnel, proxy or jump host where interactive login sessions and remote command execution are not required or desired. Only public-key authentication is supported, password logins are never accepted. An optional low-interaction honeypot mode can log or report unsolicited password authentication attempts.
Interactive shell sessions, PTY allocation, and remote command execution are all explicitly not supported.
By default, hussh binds to `[::]:2` and runs in the foreground.
OPTIONS
-c, --config PATH
-B, --bind ADDRESS
-K, --keygen
-v, --verbose
--help
--version
CONFIGURATION
The default configuration file location is /etc/hussh.conf. A minimal configuration would look like this:
[[rules]]
ssh_keys = [
"ssh-ed25519 AAAAC3Nyourkeyhere",
]
# Allowed destinations to connect to
permit = ["*"]
A more elaborate configuration could look like this:
[sshd]
# Change the ssh bind address (port 22 on ipv4 + ipv6)
bind_addr = "[::]:22"
[[rules]]
# Instead of allowing any username, require a specific value
username = "proxy"
ssh_keys = [
"ssh-ed25519 AAAAC3Nyourkeyhere",
"ssh-ed25519 AAAAC3Nanotherkey",
]
# Allowed destinations to connect to
permit = [
# All ports on specific destinations
"example.com:*",
"127.0.0.1:*",
# Filter by port
"*:443",
]
# If the previous rule didn't match, try this one next:
[[rules]]
ssh_keys = [
"ssh-ed25519 AAAAC3Nyourkeyhere",
]
permit = [
# Allow specific locations only
"127.0.0.1:8080",
"[::1]:8080",
]
RULES SYNTAX
The permit= option allows both specific destinations and wildcard expressions. The following are valid:
HOST:PORT, IP:PORT
Example: example.com:443, 127.0.0.1:22, [::1]:22
HOST:*, IP:*
Example: example.com:*, 127.0.0.1:*, [::1]:*
*:PORT
Example: *:443
*:*, *
Example: *:*, *
SSH CLIENT EXAMPLES
Set it up as a jump host for a 2nd, localhost-only SSH daemon:
cat >> ~/.ssh/config <<EOF Host example.com Hostname 192.0.2.37 ProxyCommand ssh -p 2 -W 127.0.0.1:%p -o ProxyCommand=none %h EOF
Forward a TCP connection through ssh, connect it to stdin/stdout:
Start a socks5 proxy server on localhost:1080. All connections are forwarded through the ssh server:
Listen for incoming connections on localhost:1337 and forward them to localhost:8080 of the ssh server:
HONEYPOT MODE
In addition to operating as a network proxy, hussh can also be used as a low-interaction SSH honeypot, to passively build combolists from internet noise. When enabled, it records unsolicited password authentication attempts, including the username, password and source address. This information can either be logged or forwarded as json to a remote HTTP endpoint:
# /etc/hussh.conf
[honeypot]
# Change the SSH server banner to a custom string
# Note that invalid values may confuse or break clients
spoof_server_id = "SSH-2.0-anything"
# Log unsolicited password authentication attempts (including the password) to stderr
log_bruteforce_passwords = true
# Report unsolicited password authentication attempts to a remote server via http json post:
# {"username":"root","password":"123456","src":"192.0.2.34:56789"}
report_url_bruteforce_passwords = "https://example.com/report"
# In addition to unsolicited password authentication attempts,
# advertise that password authentication is supported/enabled
bait_password_bruteforce = true
AUTHORS
This program was originally written and is currently maintained by kpcyrd. Bug reports and patches are welcome on Github:
| 2026-08-24 |