The Secure Shell program supports a number of command line flags to control behavior on a per-connection basis. These are not to be confused with the various terminal preferences (like colors or fonts).
This is a shortcut for setting other options so people don't have to remember the full list. At the moment, the only config supported is
Select the relay server implementation. For more details, see the Relay Protocol document.
For naming, we follow the convention laid out in Section 6 of RFC4251. Specifically, we add a
@google.com suffix to the names to make it clear these are extensions designed by Google rather than IETF standards. Do not confuse them with e-mail addresses.
The default value is
firstname.lastname@example.org. You can also specify
The host to use as a relay server. All connections will be made via this server.
The host to use as a fallback relay server for
The port to connect to on the relay server.
The remote ssh server for the proxy to connect to. This may be used by the proxy to redirect to the best geolocated proxy instance.
The username to use when talking to the relay server itself. This is not the same username used to connect to the ssh server.
Not all relay servers need or use this setting. If not specified, it will default to the ssh server username.
Whether to use HTTPS (the default) or HTTP when communicating with the relay server.
Even if you use HTTP, the actual ssh session will still be encrypted.
Use XML HTTP requests (XHR) when communicating with the relay server instead of WebSockets. Use of this depends on your relay server implementation.
Authentication mode to use for relay. Default is
js-redirct, set to
direct to use relay
method=direct. For more details, see the Relay Protocol document.
Report ACK latency to the relay server. If you don't know what this is for, then just ignore it.
Report connection attempt counts to the relay server. If you don't know what this is for, then just ignore it.
Whether to try to auto-resume broken relay connections.
--ssh-agent=<backend ID>,<backend ID>,...
A comma-separated list of IDs of backends to use with the builtin JS SSH agent. All agent requests are sent to all backends and their results are accumulated and relayed back to the client.
The following backends are currently implemented:
stub: A minimal implementation of a backend. Only used for testing purposes.
gsc: Supports SSH authentication using private keys stored on OpenPGP-enabled smart cards. Note: Requires the Smart Card Connector app to be installed.
The extension to use as an ssh agent. All auth requests will be forwarded from the ssh session to this extension for processing. It can be used to manage keys or certificates or anything else an ssh agent can.
Here's a list of known agents:
As a shortcut,
gnubby may be used as an alias for the autodetected extension.
The version of the ssh client to use. Intended for mitigating regressions with newer versions of the plugin and quick version comparison.
Support for older versions is not permanent and there is no guarantee that newer releases will continue to bundle them. If you encounter problems with the default version and selecting a previous version makes things work, you need to report a bug.
Here are some versions that might be available:
pnacl: The default OpenSSH version built for NaCl most people should use.
pnacl-openssh-7.5p1: An older OpenSSH release.
Display the normal welcome/tips/etc... messages when loading a connection. Users are probably interested in the
--no-welcome inverse to automatically clear all of this when connecting.
Control internal field trial settings. These are not currently documented as they aren't meant for normal users.
Control internal debug settings. These are not currently documented as they aren't meant for normal users.