Report vulnerabilities privately through GitHub Security Advisories.

Please include the version, local OS, Development Host OS, reproduction steps, and expected impact.

• SSH authentication, keys, host verification, jump hosts, and proxy settings belong to system OpenSSH. This project stores no credentials.
• Host aliases and ports are passed as an argument vector to an absolute ssh executable; no local shell interpolates them.
• The remote command is a fixed embedded script. It reads TCP listener state, the IPv6 bind mode, and best-effort executable/working-directory links from procfs. When available, ss associates sockets with same-user processes. Listeners whose executable is sshd, or that greet with an SSH identification banner on loopback, are omitted so a Development Host SSH daemon is not offered for import. When the scanning user can read the Docker engine API, published container ports may be labeled with the Compose service name and project working directory.
• Remote process metadata is bounded, UTF-8 repaired, and stripped of terminal control characters before it reaches status output. It is never persisted.
• Imported services target Development Host 127.0.0.1 but listen on local 0.0.0.0, allowing virtual machines, containers, and other connected networks to reach them. Published Forwards use explicit 127.0.0.1 endpoints at both ends. After creating a Published Forward, the Adapter verifies the actual Development Host socket through procfs before reporting it active; wildcard binds forced by GatewayPorts yes are canceled and reported. If cancellation of an installed forward fails, the product-owned SSH master is stopped so its listeners cannot remain reachable.
• The manager socket and state files are accessible only to the current OS user.
• Remote scanner frames, stderr retention, and observed listener counts are bounded.

The Manager exposes an imported remote service on every local IPv4 interface, or a local service to processes and users on the Development Host. Imported ports may be reachable from the local network; loopback-published ports are machine-local but not user-private. Configure only ports you intend to make reachable in that scope and use a host firewall on untrusted networks. TCP forwarding adds no application authentication; the forwarded service's own authentication and trust model still apply. The local Manager can connect to a configured Local Service even when that service is otherwise reachable only on local loopback.

Browser debugging endpoints grant control over their browser profile. Use a dedicated profile without sensitive browsing, publish it only to a trusted single-user Development Host, and unpublish it as soon as it is no longer needed.

Published Forwards require sshd GatewayPorts no (the default) or GatewayPorts clientspecified. GatewayPorts yes forces wildcard listeners; ssh-forward fails closed if it detects that policy or cannot verify the actual remote bind.