Annotation of src/usr.bin/ssh/ssh.1, Revision 1.365
1.1 deraadt 1: .\"
2: .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
3: .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
4: .\" All rights reserved
5: .\"
1.59 deraadt 6: .\" As far as I am concerned, the code I have written for this software
7: .\" can be used freely for any purpose. Any derived versions of this
8: .\" software must be clearly marked as such, and if the derived work is
9: .\" incompatible with the protocol description in the RFC file, it must be
10: .\" called by a name other than "ssh" or "Secure Shell".
11: .\"
1.93 deraadt 12: .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
13: .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
14: .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
1.59 deraadt 15: .\"
16: .\" Redistribution and use in source and binary forms, with or without
17: .\" modification, are permitted provided that the following conditions
18: .\" are met:
19: .\" 1. Redistributions of source code must retain the above copyright
20: .\" notice, this list of conditions and the following disclaimer.
21: .\" 2. Redistributions in binary form must reproduce the above copyright
22: .\" notice, this list of conditions and the following disclaimer in the
23: .\" documentation and/or other materials provided with the distribution.
1.1 deraadt 24: .\"
1.59 deraadt 25: .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
26: .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
27: .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
28: .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
29: .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
30: .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
31: .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
32: .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
33: .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
34: .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1.1 deraadt 35: .\"
1.365 ! mmcc 36: .\" $OpenBSD: ssh.1,v 1.364 2015/09/25 18:19:54 jmc Exp $
! 37: .Dd $Mdocdate: September 25 2015 $
1.2 deraadt 38: .Dt SSH 1
39: .Os
40: .Sh NAME
41: .Nm ssh
1.96 deraadt 42: .Nd OpenSSH SSH client (remote login program)
1.2 deraadt 43: .Sh SYNOPSIS
44: .Nm ssh
1.306 jmc 45: .Bk -words
1.351 jmc 46: .Op Fl 1246AaCfGgKkMNnqsTtVvXxYy
1.108 markus 47: .Op Fl b Ar bind_address
1.51 markus 48: .Op Fl c Ar cipher_spec
1.306 jmc 49: .Op Fl D Oo Ar bind_address : Oc Ns Ar port
1.331 dtucker 50: .Op Fl E Ar log_file
1.2 deraadt 51: .Op Fl e Ar escape_char
1.176 jmc 52: .Op Fl F Ar configfile
1.292 jmc 53: .Op Fl I Ar pkcs11
1.2 deraadt 54: .Op Fl i Ar identity_file
1.360 millert 55: .Op Fl L Ar address
1.176 jmc 56: .Op Fl l Ar login_name
57: .Op Fl m Ar mac_spec
1.198 djm 58: .Op Fl O Ar ctl_cmd
1.176 jmc 59: .Op Fl o Ar option
60: .Op Fl p Ar port
1.362 djm 61: .Op Fl Q Ar query_option
1.360 millert 62: .Op Fl R Ar address
1.198 djm 63: .Op Fl S Ar ctl_path
1.290 dtucker 64: .Op Fl W Ar host : Ns Ar port
1.306 jmc 65: .Op Fl w Ar local_tun Ns Op : Ns Ar remote_tun
1.176 jmc 66: .Oo Ar user Ns @ Oc Ns Ar hostname
1.2 deraadt 67: .Op Ar command
1.306 jmc 68: .Ek
1.44 aaron 69: .Sh DESCRIPTION
1.2 deraadt 70: .Nm
1.96 deraadt 71: (SSH client) is a program for logging into a remote machine and for
1.40 aaron 72: executing commands on a remote machine.
1.365 ! mmcc 73: It is intended to provide secure encrypted communications between
1.40 aaron 74: two untrusted hosts over an insecure network.
1.348 millert 75: X11 connections, arbitrary TCP ports and
76: .Ux Ns -domain
77: sockets can also be forwarded over the secure channel.
1.2 deraadt 78: .Pp
79: .Nm
1.44 aaron 80: connects and logs into the specified
1.176 jmc 81: .Ar hostname
82: (with optional
83: .Ar user
84: name).
1.1 deraadt 85: The user must prove
1.49 markus 86: his/her identity to the remote machine using one of several methods
1.365 ! mmcc 87: (see below).
1.49 markus 88: .Pp
1.176 jmc 89: If
90: .Ar command
91: is specified,
1.219 jmc 92: it is executed on the remote host instead of a login shell.
1.2 deraadt 93: .Pp
1.218 jmc 94: The options are as follows:
1.361 millert 95: .Pp
1.360 millert 96: .Bl -tag -width Ds -compact
1.218 jmc 97: .It Fl 1
98: Forces
1.2 deraadt 99: .Nm
1.218 jmc 100: to try protocol version 1 only.
1.360 millert 101: .Pp
1.218 jmc 102: .It Fl 2
103: Forces
1.2 deraadt 104: .Nm
1.218 jmc 105: to try protocol version 2 only.
1.360 millert 106: .Pp
1.218 jmc 107: .It Fl 4
108: Forces
1.2 deraadt 109: .Nm
1.218 jmc 110: to use IPv4 addresses only.
1.360 millert 111: .Pp
1.218 jmc 112: .It Fl 6
113: Forces
1.2 deraadt 114: .Nm
1.218 jmc 115: to use IPv6 addresses only.
1.360 millert 116: .Pp
1.218 jmc 117: .It Fl A
118: Enables forwarding of the authentication agent connection.
119: This can also be specified on a per-host basis in a configuration file.
1.2 deraadt 120: .Pp
1.218 jmc 121: Agent forwarding should be enabled with caution.
122: Users with the ability to bypass file permissions on the remote host
1.285 sobrado 123: (for the agent's
1.286 sobrado 124: .Ux Ns -domain
125: socket) can access the local agent through the forwarded connection.
1.218 jmc 126: An attacker cannot obtain key material from the agent,
127: however they can perform operations on the keys that enable them to
128: authenticate using the identities loaded into the agent.
1.360 millert 129: .Pp
1.218 jmc 130: .It Fl a
131: Disables forwarding of the authentication agent connection.
1.360 millert 132: .Pp
1.218 jmc 133: .It Fl b Ar bind_address
134: Use
135: .Ar bind_address
136: on the local machine as the source address
137: of the connection.
138: Only useful on systems with more than one address.
1.360 millert 139: .Pp
1.218 jmc 140: .It Fl C
141: Requests compression of all data (including stdin, stdout, stderr, and
1.348 millert 142: data for forwarded X11, TCP and
143: .Ux Ns -domain
144: connections).
1.218 jmc 145: The compression algorithm is the same used by
146: .Xr gzip 1 ,
147: and the
148: .Dq level
149: can be controlled by the
150: .Cm CompressionLevel
151: option for protocol version 1.
152: Compression is desirable on modem lines and other
153: slow connections, but will only slow down things on fast networks.
154: The default value can be set on a host-by-host basis in the
155: configuration files; see the
156: .Cm Compression
157: option.
1.360 millert 158: .Pp
1.218 jmc 159: .It Fl c Ar cipher_spec
160: Selects the cipher specification for encrypting the session.
1.2 deraadt 161: .Pp
1.218 jmc 162: Protocol version 1 allows specification of a single cipher.
163: The supported values are
164: .Dq 3des ,
1.220 jmc 165: .Dq blowfish ,
1.218 jmc 166: and
167: .Dq des .
1.230 jmc 168: For protocol version 2,
1.218 jmc 169: .Ar cipher_spec
170: is a comma-separated list of ciphers
171: listed in order of preference.
1.283 jmc 172: See the
173: .Cm Ciphers
1.307 dtucker 174: keyword in
175: .Xr ssh_config 5
176: for more information.
1.360 millert 177: .Pp
1.218 jmc 178: .It Fl D Xo
179: .Sm off
180: .Oo Ar bind_address : Oc
181: .Ar port
182: .Sm on
183: .Xc
184: Specifies a local
185: .Dq dynamic
186: application-level port forwarding.
187: This works by allocating a socket to listen to
188: .Ar port
189: on the local side, optionally bound to the specified
190: .Ar bind_address .
191: Whenever a connection is made to this port, the
192: connection is forwarded over the secure channel, and the application
193: protocol is then used to determine where to connect to from the
194: remote machine.
195: Currently the SOCKS4 and SOCKS5 protocols are supported, and
1.107 markus 196: .Nm
1.218 jmc 197: will act as a SOCKS server.
198: Only root can forward privileged ports.
199: Dynamic port forwardings can also be specified in the configuration file.
1.49 markus 200: .Pp
1.308 djm 201: IPv6 addresses can be specified by enclosing the address in square brackets.
1.218 jmc 202: Only the superuser can forward privileged ports.
203: By default, the local port is bound in accordance with the
204: .Cm GatewayPorts
205: setting.
206: However, an explicit
207: .Ar bind_address
208: may be used to bind the connection to a specific address.
209: The
210: .Ar bind_address
211: of
212: .Dq localhost
213: indicates that the listening port be bound for local use only, while an
214: empty address or
215: .Sq *
216: indicates that the port should be available from all interfaces.
1.360 millert 217: .Pp
1.331 dtucker 218: .It Fl E Ar log_file
219: Append debug logs to
220: .Ar log_file
221: instead of standard error.
1.360 millert 222: .Pp
1.229 jmc 223: .It Fl e Ar escape_char
1.218 jmc 224: Sets the escape character for sessions with a pty (default:
225: .Ql ~ ) .
226: The escape character is only recognized at the beginning of a line.
227: The escape character followed by a dot
228: .Pq Ql \&.
229: closes the connection;
230: followed by control-Z suspends the connection;
231: and followed by itself sends the escape character once.
232: Setting the character to
1.2 deraadt 233: .Dq none
1.218 jmc 234: disables any escapes and makes the session fully transparent.
1.360 millert 235: .Pp
1.218 jmc 236: .It Fl F Ar configfile
237: Specifies an alternative per-user configuration file.
238: If a configuration file is given on the command line,
239: the system-wide configuration file
240: .Pq Pa /etc/ssh/ssh_config
241: will be ignored.
242: The default for the per-user configuration file is
243: .Pa ~/.ssh/config .
1.360 millert 244: .Pp
1.218 jmc 245: .It Fl f
246: Requests
247: .Nm
248: to go to background just before command execution.
249: This is useful if
1.176 jmc 250: .Nm
1.218 jmc 251: is going to ask for passwords or passphrases, but the user
252: wants it in the background.
253: This implies
254: .Fl n .
255: The recommended way to start X11 programs at a remote site is with
256: something like
257: .Ic ssh -f host xterm .
1.277 djm 258: .Pp
259: If the
260: .Cm ExitOnForwardFailure
261: configuration option is set to
262: .Dq yes ,
263: then a client started with
264: .Fl f
265: will wait for all remote port forwards to be successfully established
266: before placing itself in the background.
1.360 millert 267: .Pp
1.350 djm 268: .It Fl G
269: Causes
270: .Nm
271: to print its configuration after evaluating
272: .Cm Host
273: and
274: .Cm Match
275: blocks and exit.
1.360 millert 276: .Pp
1.218 jmc 277: .It Fl g
278: Allows remote hosts to connect to local forwarded ports.
1.346 djm 279: If used on a multiplexed connection, then this option must be specified
280: on the master process.
1.360 millert 281: .Pp
1.291 markus 282: .It Fl I Ar pkcs11
1.294 jmc 283: Specify the PKCS#11 shared library
1.176 jmc 284: .Nm
1.293 markus 285: should use to communicate with a PKCS#11 token providing the user's
1.218 jmc 286: private RSA key.
1.360 millert 287: .Pp
1.218 jmc 288: .It Fl i Ar identity_file
289: Selects a file from which the identity (private key) for
1.310 djm 290: public key authentication is read.
1.218 jmc 291: The default is
292: .Pa ~/.ssh/identity
293: for protocol version 1, and
1.310 djm 294: .Pa ~/.ssh/id_dsa ,
1.343 naddy 295: .Pa ~/.ssh/id_ecdsa ,
296: .Pa ~/.ssh/id_ed25519
1.310 djm 297: and
1.218 jmc 298: .Pa ~/.ssh/id_rsa
299: for protocol version 2.
300: Identity files may also be specified on
301: a per-host basis in the configuration file.
302: It is possible to have multiple
303: .Fl i
304: options (and multiple identities specified in
305: configuration files).
1.364 jmc 306: If no certificates have been explicitly specified by the
1.363 djm 307: .Cm CertificateFile
308: directive,
1.302 djm 309: .Nm
310: will also try to load certificate information from the filename obtained
311: by appending
312: .Pa -cert.pub
313: to identity filenames.
1.360 millert 314: .Pp
1.269 djm 315: .It Fl K
316: Enables GSSAPI-based authentication and forwarding (delegation) of GSSAPI
317: credentials to the server.
1.360 millert 318: .Pp
1.218 jmc 319: .It Fl k
320: Disables forwarding (delegation) of GSSAPI credentials to the server.
1.360 millert 321: .Pp
1.218 jmc 322: .It Fl L Xo
323: .Sm off
324: .Oo Ar bind_address : Oc
325: .Ar port : host : hostport
326: .Sm on
327: .Xc
1.360 millert 328: .It Fl L Xo
329: .Sm off
330: .Oo Ar bind_address : Oc
331: .Ar port : remote_socket
332: .Sm on
333: .Xc
334: .It Fl L Xo
335: .Sm off
336: .Ar local_socket : host : hostport
337: .Sm on
338: .Xc
339: .It Fl L Xo
340: .Sm off
341: .Ar local_socket : remote_socket
342: .Sm on
343: .Xc
344: Specifies that connections to the given TCP port or Unix socket on the local
345: (client) host are to be forwarded to the given host and port, or Unix socket,
346: on the remote side.
347: This works by allocating a socket to listen to either a TCP
1.218 jmc 348: .Ar port
349: on the local side, optionally bound to the specified
1.360 millert 350: .Ar bind_address ,
351: or to a Unix socket.
352: Whenever a connection is made to the local port or socket, the
1.218 jmc 353: connection is forwarded over the secure channel, and a connection is
1.360 millert 354: made to either
1.218 jmc 355: .Ar host
356: port
1.360 millert 357: .Ar hostport ,
358: or the Unix socket
359: .Ar remote_socket ,
1.218 jmc 360: from the remote machine.
1.360 millert 361: .Pp
1.218 jmc 362: Port forwardings can also be specified in the configuration file.
1.360 millert 363: Only the superuser can forward privileged ports.
1.308 djm 364: IPv6 addresses can be specified by enclosing the address in square brackets.
1.360 millert 365: .Pp
1.218 jmc 366: By default, the local port is bound in accordance with the
367: .Cm GatewayPorts
368: setting.
369: However, an explicit
370: .Ar bind_address
371: may be used to bind the connection to a specific address.
1.2 deraadt 372: The
1.218 jmc 373: .Ar bind_address
374: of
375: .Dq localhost
376: indicates that the listening port be bound for local use only, while an
377: empty address or
378: .Sq *
379: indicates that the port should be available from all interfaces.
1.360 millert 380: .Pp
1.218 jmc 381: .It Fl l Ar login_name
382: Specifies the user to log in as on the remote machine.
383: This also may be specified on a per-host basis in the configuration file.
1.360 millert 384: .Pp
1.218 jmc 385: .It Fl M
386: Places the
387: .Nm
388: client into
389: .Dq master
390: mode for connection sharing.
1.231 stevesk 391: Multiple
392: .Fl M
393: options places
394: .Nm
395: into
396: .Dq master
397: mode with confirmation required before slave connections are accepted.
1.218 jmc 398: Refer to the description of
399: .Cm ControlMaster
400: in
401: .Xr ssh_config 5
402: for details.
1.360 millert 403: .Pp
1.218 jmc 404: .It Fl m Ar mac_spec
405: Additionally, for protocol version 2 a comma-separated list of MAC
406: (message authentication code) algorithms can
407: be specified in order of preference.
408: See the
409: .Cm MACs
410: keyword for more information.
1.360 millert 411: .Pp
1.218 jmc 412: .It Fl N
413: Do not execute a remote command.
414: This is useful for just forwarding ports
415: (protocol version 2 only).
1.360 millert 416: .Pp
1.218 jmc 417: .It Fl n
418: Redirects stdin from
419: .Pa /dev/null
420: (actually, prevents reading from stdin).
421: This must be used when
1.2 deraadt 422: .Nm
1.218 jmc 423: is run in the background.
424: A common trick is to use this to run X11 programs on a remote machine.
425: For example,
426: .Ic ssh -n shadows.cs.hut.fi emacs &
427: will start an emacs on shadows.cs.hut.fi, and the X11
428: connection will be automatically forwarded over an encrypted channel.
429: The
1.2 deraadt 430: .Nm
1.218 jmc 431: program will be put in the background.
432: (This does not work if
1.2 deraadt 433: .Nm
1.218 jmc 434: needs to ask for a password or passphrase; see also the
435: .Fl f
436: option.)
1.360 millert 437: .Pp
1.218 jmc 438: .It Fl O Ar ctl_cmd
439: Control an active connection multiplexing master process.
440: When the
441: .Fl O
442: option is specified, the
443: .Ar ctl_cmd
444: argument is interpreted and passed to the master process.
445: Valid commands are:
446: .Dq check
1.305 markus 447: (check that the master process is running),
448: .Dq forward
1.318 jmc 449: (request forwardings without command execution),
1.323 okan 450: .Dq cancel
451: (cancel forwardings),
1.218 jmc 452: .Dq exit
1.318 jmc 453: (request the master to exit), and
1.317 djm 454: .Dq stop
455: (request the master to stop accepting further multiplexing requests).
1.360 millert 456: .Pp
1.218 jmc 457: .It Fl o Ar option
458: Can be used to give options in the format used in the configuration file.
459: This is useful for specifying options for which there is no separate
460: command-line flag.
461: For full details of the options listed below, and their possible values, see
462: .Xr ssh_config 5 .
1.2 deraadt 463: .Pp
1.218 jmc 464: .Bl -tag -width Ds -offset indent -compact
465: .It AddressFamily
466: .It BatchMode
467: .It BindAddress
1.338 djm 468: .It CanonicalDomains
1.339 djm 469: .It CanonicalizeFallbackLocal
470: .It CanonicalizeHostname
471: .It CanonicalizeMaxDots
472: .It CanonicalizePermittedCNAMEs
1.363 djm 473: .It CertificateFile
1.218 jmc 474: .It ChallengeResponseAuthentication
475: .It CheckHostIP
476: .It Cipher
477: .It Ciphers
478: .It ClearAllForwardings
479: .It Compression
480: .It CompressionLevel
481: .It ConnectionAttempts
482: .It ConnectTimeout
483: .It ControlMaster
484: .It ControlPath
1.321 djm 485: .It ControlPersist
1.218 jmc 486: .It DynamicForward
487: .It EscapeChar
1.263 markus 488: .It ExitOnForwardFailure
1.353 jmc 489: .It FingerprintHash
1.218 jmc 490: .It ForwardAgent
491: .It ForwardX11
1.321 djm 492: .It ForwardX11Timeout
1.218 jmc 493: .It ForwardX11Trusted
494: .It GatewayPorts
495: .It GlobalKnownHostsFile
496: .It GSSAPIAuthentication
497: .It GSSAPIDelegateCredentials
498: .It HashKnownHosts
499: .It Host
500: .It HostbasedAuthentication
1.355 djm 501: .It HostbasedKeyTypes
1.218 jmc 502: .It HostKeyAlgorithms
503: .It HostKeyAlias
504: .It HostName
505: .It IdentityFile
506: .It IdentitiesOnly
1.316 jmc 507: .It IPQoS
1.321 djm 508: .It KbdInteractiveAuthentication
1.218 jmc 509: .It KbdInteractiveDevices
1.314 jmc 510: .It KexAlgorithms
1.218 jmc 511: .It LocalCommand
512: .It LocalForward
513: .It LogLevel
514: .It MACs
1.337 jmc 515: .It Match
1.218 jmc 516: .It NoHostAuthenticationForLocalhost
517: .It NumberOfPasswordPrompts
518: .It PasswordAuthentication
519: .It PermitLocalCommand
1.291 markus 520: .It PKCS11Provider
1.218 jmc 521: .It Port
522: .It PreferredAuthentications
523: .It Protocol
524: .It ProxyCommand
1.336 jmc 525: .It ProxyUseFdpass
1.359 markus 526: .It PubkeyAcceptedKeyTypes
1.218 jmc 527: .It PubkeyAuthentication
1.251 dtucker 528: .It RekeyLimit
1.218 jmc 529: .It RemoteForward
1.319 jmc 530: .It RequestTTY
1.218 jmc 531: .It RhostsRSAAuthentication
532: .It RSAAuthentication
533: .It SendEnv
534: .It ServerAliveInterval
535: .It ServerAliveCountMax
1.347 jmc 536: .It StreamLocalBindMask
537: .It StreamLocalBindUnlink
1.218 jmc 538: .It StrictHostKeyChecking
539: .It TCPKeepAlive
540: .It Tunnel
541: .It TunnelDevice
1.354 djm 542: .It UpdateHostKeys
1.218 jmc 543: .It UsePrivilegedPort
544: .It User
545: .It UserKnownHostsFile
546: .It VerifyHostKeyDNS
1.276 jmc 547: .It VisualHostKey
1.218 jmc 548: .It XAuthLocation
549: .El
1.360 millert 550: .Pp
1.218 jmc 551: .It Fl p Ar port
552: Port to connect to on the remote host.
553: This can be specified on a
554: per-host basis in the configuration file.
1.360 millert 555: .Pp
1.362 djm 556: .It Fl Q Ar query_option
1.332 djm 557: Queries
558: .Nm
1.341 deraadt 559: for the algorithms supported for the specified version 2.
560: The available features are:
561: .Ar cipher
1.332 djm 562: (supported symmetric ciphers),
1.341 deraadt 563: .Ar cipher-auth
1.340 djm 564: (supported symmetric ciphers that support authenticated encryption),
1.341 deraadt 565: .Ar mac
1.332 djm 566: (supported message integrity codes),
1.341 deraadt 567: .Ar kex
1.332 djm 568: (key exchange algorithms),
1.341 deraadt 569: .Ar key
1.362 djm 570: (key types),
571: .Ar key-cert
572: (certificate key types),
573: .Ar key-plain
574: (non-certificate key types), and
1.356 djm 575: .Ar protocol-version
576: (supported SSH protocol versions).
1.360 millert 577: .Pp
1.218 jmc 578: .It Fl q
579: Quiet mode.
1.271 djm 580: Causes most warning and diagnostic messages to be suppressed.
1.360 millert 581: .Pp
1.218 jmc 582: .It Fl R Xo
583: .Sm off
584: .Oo Ar bind_address : Oc
585: .Ar port : host : hostport
586: .Sm on
587: .Xc
1.360 millert 588: .It Fl R Xo
589: .Sm off
590: .Oo Ar bind_address : Oc
591: .Ar port : local_socket
592: .Sm on
593: .Xc
594: .It Fl R Xo
595: .Sm off
596: .Ar remote_socket : host : hostport
597: .Sm on
598: .Xc
599: .It Fl R Xo
600: .Sm off
601: .Ar remote_socket : local_socket
602: .Sm on
603: .Xc
604: Specifies that connections to the given TCP port or Unix socket on the remote
605: (server) host are to be forwarded to the given host and port, or Unix socket,
606: on the local side.
607: This works by allocating a socket to listen to either a TCP
1.218 jmc 608: .Ar port
1.360 millert 609: or to a Unix socket on the remote side.
610: Whenever a connection is made to this port or Unix socket, the
611: connection is forwarded over the secure channel, and a connection
612: is made to either
1.218 jmc 613: .Ar host
614: port
1.360 millert 615: .Ar hostport ,
616: or
617: .Ar local_socket ,
1.218 jmc 618: from the local machine.
1.2 deraadt 619: .Pp
1.218 jmc 620: Port forwardings can also be specified in the configuration file.
621: Privileged ports can be forwarded only when
622: logging in as root on the remote machine.
1.324 jmc 623: IPv6 addresses can be specified by enclosing the address in square brackets.
1.194 jakob 624: .Pp
1.360 millert 625: By default, TCP listening sockets on the server will be bound to the loopback
1.218 jmc 626: interface only.
1.280 tobias 627: This may be overridden by specifying a
1.218 jmc 628: .Ar bind_address .
629: An empty
630: .Ar bind_address ,
631: or the address
632: .Ql * ,
633: indicates that the remote socket should listen on all interfaces.
634: Specifying a remote
635: .Ar bind_address
636: will only succeed if the server's
637: .Cm GatewayPorts
638: option is enabled (see
639: .Xr sshd_config 5 ) .
1.281 djm 640: .Pp
641: If the
642: .Ar port
643: argument is
1.282 djm 644: .Ql 0 ,
1.281 djm 645: the listen port will be dynamically allocated on the server and reported
646: to the client at run time.
1.305 markus 647: When used together with
648: .Ic -O forward
649: the allocated port will be printed to the standard output.
1.360 millert 650: .Pp
1.218 jmc 651: .It Fl S Ar ctl_path
1.304 jmc 652: Specifies the location of a control socket for connection sharing,
1.303 djm 653: or the string
654: .Dq none
655: to disable connection sharing.
1.218 jmc 656: Refer to the description of
657: .Cm ControlPath
658: and
659: .Cm ControlMaster
660: in
661: .Xr ssh_config 5
662: for details.
1.360 millert 663: .Pp
1.218 jmc 664: .It Fl s
665: May be used to request invocation of a subsystem on the remote system.
666: Subsystems are a feature of the SSH2 protocol which facilitate the use
667: of SSH as a secure transport for other applications (eg.\&
668: .Xr sftp 1 ) .
669: The subsystem is specified as the remote command.
1.360 millert 670: .Pp
1.218 jmc 671: .It Fl T
1.357 dtucker 672: Disable pseudo-terminal allocation.
1.360 millert 673: .Pp
1.218 jmc 674: .It Fl t
1.357 dtucker 675: Force pseudo-terminal allocation.
1.218 jmc 676: This can be used to execute arbitrary
677: screen-based programs on a remote machine, which can be very useful,
1.257 jmc 678: e.g. when implementing menu services.
1.218 jmc 679: Multiple
680: .Fl t
681: options force tty allocation, even if
1.194 jakob 682: .Nm
1.218 jmc 683: has no local tty.
1.360 millert 684: .Pp
1.218 jmc 685: .It Fl V
686: Display the version number and exit.
1.360 millert 687: .Pp
1.218 jmc 688: .It Fl v
689: Verbose mode.
690: Causes
1.176 jmc 691: .Nm
1.218 jmc 692: to print debugging messages about its progress.
693: This is helpful in
694: debugging connection, authentication, and configuration problems.
695: Multiple
696: .Fl v
697: options increase the verbosity.
698: The maximum is 3.
1.360 millert 699: .Pp
1.290 dtucker 700: .It Fl W Ar host : Ns Ar port
701: Requests that standard input and output on the client be forwarded to
702: .Ar host
703: on
704: .Ar port
705: over the secure channel.
706: Implies
707: .Fl N ,
708: .Fl T ,
709: .Cm ExitOnForwardFailure
710: and
1.326 dtucker 711: .Cm ClearAllForwardings .
712: Works with Protocol version 2 only.
1.360 millert 713: .Pp
1.261 stevesk 714: .It Fl w Xo
715: .Ar local_tun Ns Op : Ns Ar remote_tun
716: .Xc
717: Requests
718: tunnel
719: device forwarding with the specified
1.218 jmc 720: .Xr tun 4
1.261 stevesk 721: devices between the client
722: .Pq Ar local_tun
723: and the server
724: .Pq Ar remote_tun .
725: .Pp
1.228 jmc 726: The devices may be specified by numerical ID or the keyword
727: .Dq any ,
728: which uses the next available tunnel device.
1.261 stevesk 729: If
730: .Ar remote_tun
731: is not specified, it defaults to
732: .Dq any .
1.228 jmc 733: See also the
1.218 jmc 734: .Cm Tunnel
1.261 stevesk 735: and
736: .Cm TunnelDevice
737: directives in
1.218 jmc 738: .Xr ssh_config 5 .
1.261 stevesk 739: If the
740: .Cm Tunnel
741: directive is unset, it is set to the default tunnel mode, which is
742: .Dq point-to-point .
1.360 millert 743: .Pp
1.218 jmc 744: .It Fl X
745: Enables X11 forwarding.
1.54 markus 746: This can also be specified on a per-host basis in a configuration file.
1.165 stevesk 747: .Pp
1.218 jmc 748: X11 forwarding should be enabled with caution.
1.168 jmc 749: Users with the ability to bypass file permissions on the remote host
1.218 jmc 750: (for the user's X authorization database)
751: can access the local X11 display through the forwarded connection.
752: An attacker may then be able to perform activities such as keystroke monitoring.
753: .Pp
754: For this reason, X11 forwarding is subjected to X11 SECURITY extension
755: restrictions by default.
756: Please refer to the
757: .Nm
758: .Fl Y
759: option and the
760: .Cm ForwardX11Trusted
761: directive in
762: .Xr ssh_config 5
763: for more information.
1.360 millert 764: .Pp
1.218 jmc 765: .It Fl x
766: Disables X11 forwarding.
1.360 millert 767: .Pp
1.218 jmc 768: .It Fl Y
769: Enables trusted X11 forwarding.
770: Trusted X11 forwardings are not subjected to the X11 SECURITY extension
771: controls.
1.360 millert 772: .Pp
1.278 djm 773: .It Fl y
774: Send log information using the
775: .Xr syslog 3
776: system module.
777: By default this information is sent to stderr.
1.218 jmc 778: .El
1.224 jmc 779: .Pp
780: .Nm
781: may additionally obtain configuration data from
782: a per-user configuration file and a system-wide configuration file.
783: The file format and configuration options are described in
784: .Xr ssh_config 5 .
1.222 jmc 785: .Sh AUTHENTICATION
1.249 jmc 786: The OpenSSH SSH client supports SSH protocols 1 and 2.
1.284 jmc 787: The default is to use protocol 2 only,
788: though this can be changed via the
1.222 jmc 789: .Cm Protocol
790: option in
1.284 jmc 791: .Xr ssh_config 5
792: or the
1.222 jmc 793: .Fl 1
794: and
795: .Fl 2
796: options (see above).
797: Both protocols support similar authentication methods,
1.284 jmc 798: but protocol 2 is the default since
1.222 jmc 799: it provides additional mechanisms for confidentiality
800: (the traffic is encrypted using AES, 3DES, Blowfish, CAST128, or Arcfour)
1.320 djm 801: and integrity (hmac-md5, hmac-sha1,
802: hmac-sha2-256, hmac-sha2-512,
1.330 markus 803: umac-64, umac-128, hmac-ripemd160).
1.222 jmc 804: Protocol 1 lacks a strong mechanism for ensuring the
805: integrity of the connection.
806: .Pp
807: The methods available for authentication are:
1.260 jmc 808: GSSAPI-based authentication,
1.222 jmc 809: host-based authentication,
810: public key authentication,
811: challenge-response authentication,
812: and password authentication.
813: Authentication methods are tried in the order specified above,
814: though protocol 2 has a configuration option to change the default order:
815: .Cm PreferredAuthentications .
816: .Pp
817: Host-based authentication works as follows:
1.218 jmc 818: If the machine the user logs in from is listed in
819: .Pa /etc/hosts.equiv
820: or
821: .Pa /etc/shosts.equiv
822: on the remote machine, and the user names are
823: the same on both sides, or if the files
824: .Pa ~/.rhosts
825: or
826: .Pa ~/.shosts
827: exist in the user's home directory on the
828: remote machine and contain a line containing the name of the client
829: machine and the name of the user on that machine, the user is
1.222 jmc 830: considered for login.
831: Additionally, the server
832: .Em must
833: be able to verify the client's
834: host key (see the description of
1.218 jmc 835: .Pa /etc/ssh/ssh_known_hosts
1.189 dtucker 836: and
1.222 jmc 837: .Pa ~/.ssh/known_hosts ,
838: below)
839: for login to be permitted.
1.218 jmc 840: This authentication method closes security holes due to IP
1.222 jmc 841: spoofing, DNS spoofing, and routing spoofing.
1.218 jmc 842: [Note to the administrator:
843: .Pa /etc/hosts.equiv ,
844: .Pa ~/.rhosts ,
845: and the rlogin/rsh protocol in general, are inherently insecure and should be
846: disabled if security is desired.]
1.189 dtucker 847: .Pp
1.222 jmc 848: Public key authentication works as follows:
849: The scheme is based on public-key cryptography,
850: using cryptosystems
851: where encryption and decryption are done using separate keys,
852: and it is unfeasible to derive the decryption key from the encryption key.
1.218 jmc 853: The idea is that each user creates a public/private
854: key pair for authentication purposes.
855: The server knows the public key, and only the user knows the private key.
1.222 jmc 856: .Nm
857: implements public key authentication protocol automatically,
1.349 sobrado 858: using one of the DSA, ECDSA, Ed25519 or RSA algorithms.
1.222 jmc 859: Protocol 1 is restricted to using only RSA keys,
1.310 djm 860: but protocol 2 may use any.
1.333 jmc 861: The HISTORY section of
1.222 jmc 862: .Xr ssl 8
1.311 jmc 863: contains a brief discussion of the DSA and RSA algorithms.
1.210 djm 864: .Pp
1.218 jmc 865: The file
866: .Pa ~/.ssh/authorized_keys
867: lists the public keys that are permitted for logging in.
868: When the user logs in, the
1.2 deraadt 869: .Nm
1.218 jmc 870: program tells the server which key pair it would like to use for
871: authentication.
1.222 jmc 872: The client proves that it has access to the private key
873: and the server checks that the corresponding public key
874: is authorized to accept the account.
1.218 jmc 875: .Pp
1.222 jmc 876: The user creates his/her key pair by running
1.218 jmc 877: .Xr ssh-keygen 1 .
878: This stores the private key in
1.207 djm 879: .Pa ~/.ssh/identity
1.222 jmc 880: (protocol 1),
881: .Pa ~/.ssh/id_dsa
882: (protocol 2 DSA),
1.310 djm 883: .Pa ~/.ssh/id_ecdsa
884: (protocol 2 ECDSA),
1.343 naddy 885: .Pa ~/.ssh/id_ed25519
1.349 sobrado 886: (protocol 2 Ed25519),
1.222 jmc 887: or
888: .Pa ~/.ssh/id_rsa
889: (protocol 2 RSA)
1.218 jmc 890: and stores the public key in
891: .Pa ~/.ssh/identity.pub
1.222 jmc 892: (protocol 1),
893: .Pa ~/.ssh/id_dsa.pub
894: (protocol 2 DSA),
1.310 djm 895: .Pa ~/.ssh/id_ecdsa.pub
896: (protocol 2 ECDSA),
1.343 naddy 897: .Pa ~/.ssh/id_ed25519.pub
1.349 sobrado 898: (protocol 2 Ed25519),
1.222 jmc 899: or
900: .Pa ~/.ssh/id_rsa.pub
901: (protocol 2 RSA)
1.218 jmc 902: in the user's home directory.
1.222 jmc 903: The user should then copy the public key
1.218 jmc 904: to
905: .Pa ~/.ssh/authorized_keys
1.222 jmc 906: in his/her home directory on the remote machine.
907: The
1.218 jmc 908: .Pa authorized_keys
909: file corresponds to the conventional
910: .Pa ~/.rhosts
911: file, and has one key
1.222 jmc 912: per line, though the lines can be very long.
1.218 jmc 913: After this, the user can log in without giving the password.
914: .Pp
1.301 jmc 915: A variation on public key authentication
916: is available in the form of certificate authentication:
917: instead of a set of public/private keys,
918: signed certificates are used.
919: This has the advantage that a single trusted certification authority
920: can be used in place of many public/private keys.
1.333 jmc 921: See the CERTIFICATES section of
1.301 jmc 922: .Xr ssh-keygen 1
923: for more information.
924: .Pp
925: The most convenient way to use public key or certificate authentication
926: may be with an authentication agent.
1.218 jmc 927: See
928: .Xr ssh-agent 1
929: for more information.
930: .Pp
1.222 jmc 931: Challenge-response authentication works as follows:
932: The server sends an arbitrary
933: .Qq challenge
934: text, and prompts for a response.
935: Protocol 2 allows multiple challenges and responses;
936: protocol 1 is restricted to just one challenge/response.
937: Examples of challenge-response authentication include
1.335 jmc 938: .Bx
939: Authentication (see
1.222 jmc 940: .Xr login.conf 5 )
1.335 jmc 941: and PAM (some
942: .Pf non- Ox
943: systems).
1.222 jmc 944: .Pp
945: Finally, if other authentication methods fail,
1.218 jmc 946: .Nm
947: prompts the user for a password.
948: The password is sent to the remote
949: host for checking; however, since all communications are encrypted,
950: the password cannot be seen by someone listening on the network.
1.232 jmc 951: .Pp
952: .Nm
953: automatically maintains and checks a database containing
954: identification for all hosts it has ever been used with.
955: Host keys are stored in
956: .Pa ~/.ssh/known_hosts
957: in the user's home directory.
958: Additionally, the file
959: .Pa /etc/ssh/ssh_known_hosts
960: is automatically checked for known hosts.
961: Any new hosts are automatically added to the user's file.
962: If a host's identification ever changes,
963: .Nm
964: warns about this and disables password authentication to prevent
965: server spoofing or man-in-the-middle attacks,
966: which could otherwise be used to circumvent the encryption.
967: The
968: .Cm StrictHostKeyChecking
969: option can be used to control logins to machines whose
970: host key is not known or has changed.
971: .Pp
1.218 jmc 972: When the user's identity has been accepted by the server, the server
1.357 dtucker 973: either executes the given command in a non-interactive session or,
974: if no command has been specified, logs into the machine and gives
975: the user a normal shell as an interactive session.
1.218 jmc 976: All communication with
977: the remote command or shell will be automatically encrypted.
978: .Pp
1.357 dtucker 979: If an interactive session is requested
980: .Nm
981: by default will only request a pseudo-terminal (pty) for interactive
982: sessions when the client has one.
983: The flags
984: .Fl T
985: and
986: .Fl t
987: can be used to override this behaviour.
988: .Pp
989: If a pseudo-terminal has been allocated the
1.218 jmc 990: user may use the escape characters noted below.
991: .Pp
1.357 dtucker 992: If no pseudo-terminal has been allocated,
1.218 jmc 993: the session is transparent and can be used to reliably transfer binary data.
994: On most systems, setting the escape character to
995: .Dq none
996: will also make the session transparent even if a tty is used.
997: .Pp
998: The session terminates when the command or shell on the remote
1.247 jmc 999: machine exits and all X11 and TCP connections have been closed.
1.223 jmc 1000: .Sh ESCAPE CHARACTERS
1.218 jmc 1001: When a pseudo-terminal has been requested,
1.2 deraadt 1002: .Nm
1.218 jmc 1003: supports a number of functions through the use of an escape character.
1004: .Pp
1005: A single tilde character can be sent as
1006: .Ic ~~
1007: or by following the tilde by a character other than those described below.
1008: The escape character must always follow a newline to be interpreted as
1009: special.
1010: The escape character can be changed in configuration files using the
1011: .Cm EscapeChar
1012: configuration directive or on the command line by the
1013: .Fl e
1014: option.
1015: .Pp
1016: The supported escapes (assuming the default
1017: .Ql ~ )
1018: are:
1019: .Bl -tag -width Ds
1020: .It Cm ~.
1021: Disconnect.
1022: .It Cm ~^Z
1023: Background
1.234 jmc 1024: .Nm .
1.218 jmc 1025: .It Cm ~#
1026: List forwarded connections.
1027: .It Cm ~&
1028: Background
1.2 deraadt 1029: .Nm
1.218 jmc 1030: at logout when waiting for forwarded connection / X11 sessions to terminate.
1031: .It Cm ~?
1032: Display a list of escape characters.
1033: .It Cm ~B
1034: Send a BREAK to the remote system
1035: (only useful for SSH protocol version 2 and if the peer supports it).
1036: .It Cm ~C
1037: Open command line.
1038: Currently this allows the addition of port forwardings using the
1.279 stevesk 1039: .Fl L ,
1040: .Fl R
1.218 jmc 1041: and
1.279 stevesk 1042: .Fl D
1.225 jmc 1043: options (see above).
1.322 markus 1044: It also allows the cancellation of existing port-forwardings
1045: with
1.262 stevesk 1046: .Sm off
1.322 markus 1047: .Fl KL Oo Ar bind_address : Oc Ar port
1.262 stevesk 1048: .Sm on
1.322 markus 1049: for local,
1050: .Sm off
1051: .Fl KR Oo Ar bind_address : Oc Ar port
1052: .Sm on
1053: for remote and
1054: .Sm off
1055: .Fl KD Oo Ar bind_address : Oc Ar port
1056: .Sm on
1057: for dynamic port-forwardings.
1.218 jmc 1058: .Ic !\& Ns Ar command
1059: allows the user to execute a local command if the
1060: .Ic PermitLocalCommand
1061: option is enabled in
1.176 jmc 1062: .Xr ssh_config 5 .
1.218 jmc 1063: Basic help is available, using the
1064: .Fl h
1065: option.
1066: .It Cm ~R
1067: Request rekeying of the connection
1068: (only useful for SSH protocol version 2 and if the peer supports it).
1.327 dtucker 1069: .It Cm ~V
1070: Decrease the verbosity
1071: .Pq Ic LogLevel
1072: when errors are being written to stderr.
1073: .It Cm ~v
1.328 jmc 1074: Increase the verbosity
1.327 dtucker 1075: .Pq Ic LogLevel
1076: when errors are being written to stderr.
1.176 jmc 1077: .El
1.246 jmc 1078: .Sh TCP FORWARDING
1079: Forwarding of arbitrary TCP connections over the secure channel can
1080: be specified either on the command line or in a configuration file.
1081: One possible application of TCP forwarding is a secure connection to a
1082: mail server; another is going through firewalls.
1083: .Pp
1084: In the example below, we look at encrypting communication between
1085: an IRC client and server, even though the IRC server does not directly
1086: support encrypted communications.
1087: This works as follows:
1088: the user connects to the remote host using
1089: .Nm ,
1090: specifying a port to be used to forward connections
1091: to the remote server.
1092: After that it is possible to start the service which is to be encrypted
1093: on the client machine,
1094: connecting to the same local port,
1095: and
1096: .Nm
1097: will encrypt and forward the connection.
1098: .Pp
1099: The following example tunnels an IRC session from client machine
1100: .Dq 127.0.0.1
1101: (localhost)
1102: to remote server
1103: .Dq server.example.com :
1104: .Bd -literal -offset 4n
1105: $ ssh -f -L 1234:localhost:6667 server.example.com sleep 10
1106: $ irc -c '#users' -p 1234 pinky 127.0.0.1
1107: .Ed
1108: .Pp
1109: This tunnels a connection to IRC server
1110: .Dq server.example.com ,
1111: joining channel
1112: .Dq #users ,
1113: nickname
1114: .Dq pinky ,
1115: using port 1234.
1116: It doesn't matter which port is used,
1117: as long as it's greater than 1023
1118: (remember, only root can open sockets on privileged ports)
1119: and doesn't conflict with any ports already in use.
1120: The connection is forwarded to port 6667 on the remote server,
1121: since that's the standard port for IRC services.
1122: .Pp
1123: The
1124: .Fl f
1125: option backgrounds
1126: .Nm
1127: and the remote command
1128: .Dq sleep 10
1129: is specified to allow an amount of time
1130: (10 seconds, in the example)
1131: to start the service which is to be tunnelled.
1132: If no connections are made within the time specified,
1133: .Nm
1134: will exit.
1135: .Sh X11 FORWARDING
1.218 jmc 1136: If the
1137: .Cm ForwardX11
1138: variable is set to
1139: .Dq yes
1140: (or see the description of the
1.227 jmc 1141: .Fl X ,
1142: .Fl x ,
1.218 jmc 1143: and
1.227 jmc 1144: .Fl Y
1.226 jmc 1145: options above)
1.218 jmc 1146: and the user is using X11 (the
1147: .Ev DISPLAY
1148: environment variable is set), the connection to the X11 display is
1149: automatically forwarded to the remote side in such a way that any X11
1150: programs started from the shell (or command) will go through the
1151: encrypted channel, and the connection to the real X server will be made
1.176 jmc 1152: from the local machine.
1.218 jmc 1153: The user should not manually set
1154: .Ev DISPLAY .
1155: Forwarding of X11 connections can be
1156: configured on the command line or in configuration files.
1157: .Pp
1158: The
1159: .Ev DISPLAY
1160: value set by
1161: .Nm
1162: will point to the server machine, but with a display number greater than zero.
1163: This is normal, and happens because
1164: .Nm
1165: creates a
1166: .Dq proxy
1167: X server on the server machine for forwarding the
1168: connections over the encrypted channel.
1.200 djm 1169: .Pp
1.218 jmc 1170: .Nm
1171: will also automatically set up Xauthority data on the server machine.
1172: For this purpose, it will generate a random authorization cookie,
1173: store it in Xauthority on the server, and verify that any forwarded
1174: connections carry this cookie and replace it by the real cookie when
1175: the connection is opened.
1176: The real authentication cookie is never
1177: sent to the server machine (and no cookies are sent in the plain).
1.200 djm 1178: .Pp
1.218 jmc 1179: If the
1180: .Cm ForwardAgent
1181: variable is set to
1182: .Dq yes
1183: (or see the description of the
1184: .Fl A
1.191 djm 1185: and
1.218 jmc 1186: .Fl a
1.226 jmc 1187: options above) and
1.218 jmc 1188: the user is using an authentication agent, the connection to the agent
1189: is automatically forwarded to the remote side.
1.252 jmc 1190: .Sh VERIFYING HOST KEYS
1191: When connecting to a server for the first time,
1192: a fingerprint of the server's public key is presented to the user
1193: (unless the option
1194: .Cm StrictHostKeyChecking
1195: has been disabled).
1196: Fingerprints can be determined using
1197: .Xr ssh-keygen 1 :
1198: .Pp
1199: .Dl $ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key
1200: .Pp
1.274 grunk 1201: If the fingerprint is already known, it can be matched
1202: and the key can be accepted or rejected.
1.358 djm 1203: If only legacy (MD5) fingerprints for the server are available, the
1204: .Xr ssh-keygen 1
1205: .Fl E
1206: option may be used to downgrade the fingerprint algorithm to match.
1207: .Pp
1.274 grunk 1208: Because of the difficulty of comparing host keys
1.352 djm 1209: just by looking at fingerprint strings,
1.274 grunk 1210: there is also support to compare host keys visually,
1211: using
1212: .Em random art .
1213: By setting the
1.275 grunk 1214: .Cm VisualHostKey
1.274 grunk 1215: option to
1.275 grunk 1216: .Dq yes ,
1.274 grunk 1217: a small ASCII graphic gets displayed on every login to a server, no matter
1218: if the session itself is interactive or not.
1219: By learning the pattern a known server produces, a user can easily
1220: find out that the host key has changed when a completely different pattern
1221: is displayed.
1222: Because these patterns are not unambiguous however, a pattern that looks
1223: similar to the pattern remembered only gives a good probability that the
1224: host key is the same, not guaranteed proof.
1225: .Pp
1226: To get a listing of the fingerprints along with their random art for
1227: all known hosts, the following command line can be used:
1228: .Pp
1229: .Dl $ ssh-keygen -lv -f ~/.ssh/known_hosts
1230: .Pp
1.252 jmc 1231: If the fingerprint is unknown,
1232: an alternative method of verification is available:
1233: SSH fingerprints verified by DNS.
1234: An additional resource record (RR),
1235: SSHFP,
1236: is added to a zonefile
1237: and the connecting client is able to match the fingerprint
1238: with that of the key presented.
1239: .Pp
1240: In this example, we are connecting a client to a server,
1241: .Dq host.example.com .
1242: The SSHFP resource records should first be added to the zonefile for
1243: host.example.com:
1244: .Bd -literal -offset indent
1.259 jakob 1245: $ ssh-keygen -r host.example.com.
1.252 jmc 1246: .Ed
1247: .Pp
1248: The output lines will have to be added to the zonefile.
1249: To check that the zone is answering fingerprint queries:
1250: .Pp
1251: .Dl $ dig -t SSHFP host.example.com
1252: .Pp
1253: Finally the client connects:
1254: .Bd -literal -offset indent
1255: $ ssh -o "VerifyHostKeyDNS ask" host.example.com
1256: [...]
1257: Matching host key fingerprint found in DNS.
1258: Are you sure you want to continue connecting (yes/no)?
1259: .Ed
1260: .Pp
1261: See the
1262: .Cm VerifyHostKeyDNS
1263: option in
1264: .Xr ssh_config 5
1265: for more information.
1.250 jmc 1266: .Sh SSH-BASED VIRTUAL PRIVATE NETWORKS
1267: .Nm
1268: contains support for Virtual Private Network (VPN) tunnelling
1269: using the
1270: .Xr tun 4
1271: network pseudo-device,
1272: allowing two networks to be joined securely.
1273: The
1274: .Xr sshd_config 5
1275: configuration option
1276: .Cm PermitTunnel
1277: controls whether the server supports this,
1278: and at what level (layer 2 or 3 traffic).
1279: .Pp
1280: The following example would connect client network 10.0.50.0/24
1.265 otto 1281: with remote network 10.0.99.0/24 using a point-to-point connection
1282: from 10.1.1.1 to 10.1.1.2,
1283: provided that the SSH server running on the gateway to the remote network,
1284: at 192.168.1.15, allows it.
1285: .Pp
1286: On the client:
1.250 jmc 1287: .Bd -literal -offset indent
1288: # ssh -f -w 0:1 192.168.1.15 true
1.265 otto 1289: # ifconfig tun0 10.1.1.1 10.1.1.2 netmask 255.255.255.252
1290: # route add 10.0.99.0/24 10.1.1.2
1291: .Ed
1292: .Pp
1293: On the server:
1294: .Bd -literal -offset indent
1295: # ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.252
1296: # route add 10.0.50.0/24 10.1.1.1
1.250 jmc 1297: .Ed
1298: .Pp
1299: Client access may be more finely tuned via the
1300: .Pa /root/.ssh/authorized_keys
1301: file (see below) and the
1302: .Cm PermitRootLogin
1303: server option.
1.255 jmc 1304: The following entry would permit connections on
1.250 jmc 1305: .Xr tun 4
1.255 jmc 1306: device 1 from user
1.250 jmc 1307: .Dq jane
1.255 jmc 1308: and on tun device 2 from user
1.250 jmc 1309: .Dq john ,
1310: if
1311: .Cm PermitRootLogin
1312: is set to
1313: .Dq forced-commands-only :
1314: .Bd -literal -offset 2n
1315: tunnel="1",command="sh /etc/netstart tun1" ssh-rsa ... jane
1.254 msf 1316: tunnel="2",command="sh /etc/netstart tun2" ssh-rsa ... john
1.250 jmc 1317: .Ed
1318: .Pp
1.264 ray 1319: Since an SSH-based setup entails a fair amount of overhead,
1.250 jmc 1320: it may be more suited to temporary setups,
1321: such as for wireless VPNs.
1322: More permanent VPNs are better provided by tools such as
1323: .Xr ipsecctl 8
1324: and
1325: .Xr isakmpd 8 .
1.2 deraadt 1326: .Sh ENVIRONMENT
1327: .Nm
1.1 deraadt 1328: will normally set the following environment variables:
1.237 jmc 1329: .Bl -tag -width "SSH_ORIGINAL_COMMAND"
1.2 deraadt 1330: .It Ev DISPLAY
1331: The
1332: .Ev DISPLAY
1.40 aaron 1333: variable indicates the location of the X11 server.
1.44 aaron 1334: It is automatically set by
1.2 deraadt 1335: .Nm
1336: to point to a value of the form
1.233 jmc 1337: .Dq hostname:n ,
1338: where
1339: .Dq hostname
1340: indicates the host where the shell runs, and
1341: .Sq n
1342: is an integer \*(Ge 1.
1.40 aaron 1343: .Nm
1344: uses this special value to forward X11 connections over the secure
1345: channel.
1.107 markus 1346: The user should normally not set
1347: .Ev DISPLAY
1348: explicitly, as that
1.1 deraadt 1349: will render the X11 connection insecure (and will require the user to
1350: manually copy any required authorization cookies).
1.2 deraadt 1351: .It Ev HOME
1.1 deraadt 1352: Set to the path of the user's home directory.
1.2 deraadt 1353: .It Ev LOGNAME
1354: Synonym for
1.12 aaron 1355: .Ev USER ;
1356: set for compatibility with systems that use this variable.
1.2 deraadt 1357: .It Ev MAIL
1.129 stevesk 1358: Set to the path of the user's mailbox.
1.40 aaron 1359: .It Ev PATH
1.2 deraadt 1360: Set to the default
1361: .Ev PATH ,
1362: as specified when compiling
1.234 jmc 1363: .Nm .
1.118 markus 1364: .It Ev SSH_ASKPASS
1365: If
1366: .Nm
1367: needs a passphrase, it will read the passphrase from the current
1368: terminal if it was run from a terminal.
1369: If
1370: .Nm
1371: does not have a terminal associated with it but
1372: .Ev DISPLAY
1373: and
1374: .Ev SSH_ASKPASS
1375: are set, it will execute the program specified by
1376: .Ev SSH_ASKPASS
1377: and open an X11 window to read the passphrase.
1378: This is particularly useful when calling
1379: .Nm
1380: from a
1.196 jmc 1381: .Pa .xsession
1.118 markus 1382: or related script.
1383: (Note that on some machines it
1384: may be necessary to redirect the input from
1385: .Pa /dev/null
1386: to make this work.)
1.18 markus 1387: .It Ev SSH_AUTH_SOCK
1.233 jmc 1388: Identifies the path of a
1389: .Ux Ns -domain
1390: socket used to communicate with the agent.
1.166 stevesk 1391: .It Ev SSH_CONNECTION
1392: Identifies the client and server ends of the connection.
1.40 aaron 1393: The variable contains
1.233 jmc 1394: four space-separated values: client IP address, client port number,
1395: server IP address, and server port number.
1.73 markus 1396: .It Ev SSH_ORIGINAL_COMMAND
1.233 jmc 1397: This variable contains the original command line if a forced command
1.73 markus 1398: is executed.
1399: It can be used to extract the original arguments.
1.2 deraadt 1400: .It Ev SSH_TTY
1.1 deraadt 1401: This is set to the name of the tty (path to the device) associated
1.40 aaron 1402: with the current shell or command.
1403: If the current session has no tty,
1.1 deraadt 1404: this variable is not set.
1.2 deraadt 1405: .It Ev TZ
1.214 jmc 1406: This variable is set to indicate the present time zone if it
1.257 jmc 1407: was set when the daemon was started (i.e. the daemon passes the value
1.1 deraadt 1408: on to new connections).
1.2 deraadt 1409: .It Ev USER
1.1 deraadt 1410: Set to the name of the user logging in.
1.2 deraadt 1411: .El
1412: .Pp
1.44 aaron 1413: Additionally,
1.2 deraadt 1414: .Nm
1.44 aaron 1415: reads
1.207 djm 1416: .Pa ~/.ssh/environment ,
1.2 deraadt 1417: and adds lines of the format
1418: .Dq VARNAME=value
1.233 jmc 1419: to the environment if the file exists and users are allowed to
1.161 marc 1420: change their environment.
1.176 jmc 1421: For more information, see the
1.161 marc 1422: .Cm PermitUserEnvironment
1.162 stevesk 1423: option in
1.161 marc 1424: .Xr sshd_config 5 .
1.2 deraadt 1425: .Sh FILES
1.236 jmc 1426: .Bl -tag -width Ds -compact
1.309 jmc 1427: .It Pa ~/.rhosts
1.240 jmc 1428: This file is used for host-based authentication (see above).
1.92 markus 1429: On some machines this file may need to be
1.240 jmc 1430: world-readable if the user's home directory is on an NFS partition,
1.1 deraadt 1431: because
1.2 deraadt 1432: .Xr sshd 8
1.40 aaron 1433: reads it as root.
1434: Additionally, this file must be owned by the user,
1435: and must not have write permissions for anyone else.
1436: The recommended
1.1 deraadt 1437: permission for most machines is read/write for the user, and not
1438: accessible by others.
1.2 deraadt 1439: .Pp
1.309 jmc 1440: .It Pa ~/.shosts
1.240 jmc 1441: This file is used in exactly the same way as
1442: .Pa .rhosts ,
1443: but allows host-based authentication without permitting login with
1444: rlogin/rsh.
1.272 mcbride 1445: .Pp
1.309 jmc 1446: .It Pa ~/.ssh/
1.272 mcbride 1447: This directory is the default location for all user-specific configuration
1448: and authentication information.
1449: There is no general requirement to keep the entire contents of this directory
1450: secret, but the recommended permissions are read/write/execute for the user,
1451: and not accessible by others.
1.236 jmc 1452: .Pp
1.309 jmc 1453: .It Pa ~/.ssh/authorized_keys
1.349 sobrado 1454: Lists the public keys (DSA, ECDSA, Ed25519, RSA)
1.343 naddy 1455: that can be used for logging in as this user.
1.238 jmc 1456: The format of this file is described in the
1457: .Xr sshd 8
1458: manual page.
1459: This file is not highly sensitive, but the recommended
1460: permissions are read/write for the user, and not accessible by others.
1461: .Pp
1.309 jmc 1462: .It Pa ~/.ssh/config
1.238 jmc 1463: This is the per-user configuration file.
1464: The file format and configuration options are described in
1465: .Xr ssh_config 5 .
1466: Because of the potential for abuse, this file must have strict permissions:
1.334 djm 1467: read/write for the user, and not writable by others.
1.238 jmc 1468: .Pp
1.309 jmc 1469: .It Pa ~/.ssh/environment
1.239 jmc 1470: Contains additional definitions for environment variables; see
1471: .Sx ENVIRONMENT ,
1.238 jmc 1472: above.
1473: .Pp
1.309 jmc 1474: .It Pa ~/.ssh/identity
1475: .It Pa ~/.ssh/id_dsa
1.310 djm 1476: .It Pa ~/.ssh/id_ecdsa
1.343 naddy 1477: .It Pa ~/.ssh/id_ed25519
1.309 jmc 1478: .It Pa ~/.ssh/id_rsa
1.238 jmc 1479: Contains the private key for authentication.
1480: These files
1481: contain sensitive data and should be readable by the user but not
1482: accessible by others (read/write/execute).
1483: .Nm
1484: will simply ignore a private key file if it is accessible by others.
1485: It is possible to specify a passphrase when
1486: generating the key which will be used to encrypt the
1487: sensitive part of this file using 3DES.
1488: .Pp
1.309 jmc 1489: .It Pa ~/.ssh/identity.pub
1490: .It Pa ~/.ssh/id_dsa.pub
1.310 djm 1491: .It Pa ~/.ssh/id_ecdsa.pub
1.343 naddy 1492: .It Pa ~/.ssh/id_ed25519.pub
1.309 jmc 1493: .It Pa ~/.ssh/id_rsa.pub
1.238 jmc 1494: Contains the public key for authentication.
1495: These files are not
1496: sensitive and can (but need not) be readable by anyone.
1497: .Pp
1.309 jmc 1498: .It Pa ~/.ssh/known_hosts
1.244 jmc 1499: Contains a list of host keys for all hosts the user has logged into
1500: that are not already in the systemwide list of known host keys.
1.238 jmc 1501: See
1.244 jmc 1502: .Xr sshd 8
1503: for further details of the format of this file.
1.238 jmc 1504: .Pp
1.309 jmc 1505: .It Pa ~/.ssh/rc
1.238 jmc 1506: Commands in this file are executed by
1507: .Nm
1.245 jmc 1508: when the user logs in, just before the user's shell (or command) is
1.238 jmc 1509: started.
1510: See the
1511: .Xr sshd 8
1512: manual page for more information.
1513: .Pp
1.309 jmc 1514: .It Pa /etc/hosts.equiv
1.240 jmc 1515: This file is for host-based authentication (see above).
1516: It should only be writable by root.
1.236 jmc 1517: .Pp
1.309 jmc 1518: .It Pa /etc/shosts.equiv
1.240 jmc 1519: This file is used in exactly the same way as
1520: .Pa hosts.equiv ,
1521: but allows host-based authentication without permitting login with
1522: rlogin/rsh.
1.236 jmc 1523: .Pp
1.238 jmc 1524: .It Pa /etc/ssh/ssh_config
1525: Systemwide configuration file.
1526: The file format and configuration options are described in
1527: .Xr ssh_config 5 .
1528: .Pp
1.309 jmc 1529: .It Pa /etc/ssh/ssh_host_key
1530: .It Pa /etc/ssh/ssh_host_dsa_key
1.310 djm 1531: .It Pa /etc/ssh/ssh_host_ecdsa_key
1.343 naddy 1532: .It Pa /etc/ssh/ssh_host_ed25519_key
1.309 jmc 1533: .It Pa /etc/ssh/ssh_host_rsa_key
1.325 dtucker 1534: These files contain the private parts of the host keys
1.245 jmc 1535: and are used for host-based authentication.
1536: If protocol version 1 is used,
1.238 jmc 1537: .Nm
1538: must be setuid root, since the host key is readable only by root.
1539: For protocol version 2,
1540: .Nm
1541: uses
1542: .Xr ssh-keysign 8
1.245 jmc 1543: to access the host keys,
1544: eliminating the requirement that
1.238 jmc 1545: .Nm
1.245 jmc 1546: be setuid root when host-based authentication is used.
1.238 jmc 1547: By default
1.2 deraadt 1548: .Nm
1.238 jmc 1549: is not setuid root.
1550: .Pp
1.309 jmc 1551: .It Pa /etc/ssh/ssh_known_hosts
1.238 jmc 1552: Systemwide list of known host keys.
1553: This file should be prepared by the
1554: system administrator to contain the public host keys of all machines in the
1555: organization.
1.244 jmc 1556: It should be world-readable.
1557: See
1.238 jmc 1558: .Xr sshd 8
1.244 jmc 1559: for further details of the format of this file.
1.236 jmc 1560: .Pp
1.309 jmc 1561: .It Pa /etc/ssh/sshrc
1.1 deraadt 1562: Commands in this file are executed by
1.2 deraadt 1563: .Nm
1.245 jmc 1564: when the user logs in, just before the user's shell (or command) is started.
1.44 aaron 1565: See the
1.2 deraadt 1566: .Xr sshd 8
1.1 deraadt 1567: manual page for more information.
1.58 itojun 1568: .El
1.312 jmc 1569: .Sh EXIT STATUS
1570: .Nm
1571: exits with the exit status of the remote command or with 255
1572: if an error occurred.
1.2 deraadt 1573: .Sh SEE ALSO
1574: .Xr scp 1 ,
1.83 djm 1575: .Xr sftp 1 ,
1.2 deraadt 1576: .Xr ssh-add 1 ,
1577: .Xr ssh-agent 1 ,
1578: .Xr ssh-keygen 1 ,
1.242 jmc 1579: .Xr ssh-keyscan 1 ,
1.250 jmc 1580: .Xr tun 4 ,
1.159 stevesk 1581: .Xr ssh_config 5 ,
1.160 naddy 1582: .Xr ssh-keysign 8 ,
1.87 itojun 1583: .Xr sshd 8
1.329 jmc 1584: .Sh STANDARDS
1.106 markus 1585: .Rs
1.329 jmc 1586: .%A S. Lehtinen
1587: .%A C. Lonvick
1588: .%D January 2006
1.256 jmc 1589: .%R RFC 4250
1.329 jmc 1590: .%T The Secure Shell (SSH) Protocol Assigned Numbers
1.256 jmc 1591: .Re
1.329 jmc 1592: .Pp
1.256 jmc 1593: .Rs
1.329 jmc 1594: .%A T. Ylonen
1595: .%A C. Lonvick
1596: .%D January 2006
1.256 jmc 1597: .%R RFC 4251
1.329 jmc 1598: .%T The Secure Shell (SSH) Protocol Architecture
1.256 jmc 1599: .Re
1.329 jmc 1600: .Pp
1.256 jmc 1601: .Rs
1.329 jmc 1602: .%A T. Ylonen
1603: .%A C. Lonvick
1604: .%D January 2006
1.256 jmc 1605: .%R RFC 4252
1.329 jmc 1606: .%T The Secure Shell (SSH) Authentication Protocol
1.256 jmc 1607: .Re
1.329 jmc 1608: .Pp
1.256 jmc 1609: .Rs
1.329 jmc 1610: .%A T. Ylonen
1611: .%A C. Lonvick
1612: .%D January 2006
1.256 jmc 1613: .%R RFC 4253
1.329 jmc 1614: .%T The Secure Shell (SSH) Transport Layer Protocol
1.256 jmc 1615: .Re
1.329 jmc 1616: .Pp
1.256 jmc 1617: .Rs
1.329 jmc 1618: .%A T. Ylonen
1619: .%A C. Lonvick
1620: .%D January 2006
1.256 jmc 1621: .%R RFC 4254
1.329 jmc 1622: .%T The Secure Shell (SSH) Connection Protocol
1.256 jmc 1623: .Re
1.329 jmc 1624: .Pp
1.256 jmc 1625: .Rs
1.329 jmc 1626: .%A J. Schlyter
1627: .%A W. Griffin
1628: .%D January 2006
1.256 jmc 1629: .%R RFC 4255
1.329 jmc 1630: .%T Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
1.256 jmc 1631: .Re
1.329 jmc 1632: .Pp
1.256 jmc 1633: .Rs
1.329 jmc 1634: .%A F. Cusack
1635: .%A M. Forssen
1636: .%D January 2006
1.256 jmc 1637: .%R RFC 4256
1.329 jmc 1638: .%T Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)
1.256 jmc 1639: .Re
1.329 jmc 1640: .Pp
1.256 jmc 1641: .Rs
1.329 jmc 1642: .%A J. Galbraith
1643: .%A P. Remaker
1644: .%D January 2006
1.256 jmc 1645: .%R RFC 4335
1.329 jmc 1646: .%T The Secure Shell (SSH) Session Channel Break Extension
1.256 jmc 1647: .Re
1.329 jmc 1648: .Pp
1.256 jmc 1649: .Rs
1.329 jmc 1650: .%A M. Bellare
1651: .%A T. Kohno
1652: .%A C. Namprempre
1653: .%D January 2006
1.256 jmc 1654: .%R RFC 4344
1.329 jmc 1655: .%T The Secure Shell (SSH) Transport Layer Encryption Modes
1.256 jmc 1656: .Re
1.329 jmc 1657: .Pp
1.256 jmc 1658: .Rs
1.329 jmc 1659: .%A B. Harris
1660: .%D January 2006
1.256 jmc 1661: .%R RFC 4345
1.329 jmc 1662: .%T Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol
1.258 djm 1663: .Re
1.329 jmc 1664: .Pp
1.258 djm 1665: .Rs
1.329 jmc 1666: .%A M. Friedl
1667: .%A N. Provos
1668: .%A W. Simpson
1669: .%D March 2006
1.258 djm 1670: .%R RFC 4419
1.329 jmc 1671: .%T Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol
1.266 markus 1672: .Re
1.329 jmc 1673: .Pp
1.266 markus 1674: .Rs
1.329 jmc 1675: .%A J. Galbraith
1676: .%A R. Thayer
1677: .%D November 2006
1.266 markus 1678: .%R RFC 4716
1.329 jmc 1679: .%T The Secure Shell (SSH) Public Key File Format
1.313 djm 1680: .Re
1.329 jmc 1681: .Pp
1.313 djm 1682: .Rs
1.329 jmc 1683: .%A D. Stebila
1684: .%A J. Green
1685: .%D December 2009
1.313 djm 1686: .%R RFC 5656
1.329 jmc 1687: .%T Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer
1.274 grunk 1688: .Re
1.329 jmc 1689: .Pp
1.274 grunk 1690: .Rs
1691: .%A A. Perrig
1692: .%A D. Song
1693: .%D 1999
1.329 jmc 1694: .%O International Workshop on Cryptographic Techniques and E-Commerce (CrypTEC '99)
1695: .%T Hash Visualization: a New Technique to improve Real-World Security
1.106 markus 1696: .Re
1.173 jmc 1697: .Sh AUTHORS
1698: OpenSSH is a derivative of the original and free
1699: ssh 1.2.12 release by Tatu Ylonen.
1700: Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1701: Theo de Raadt and Dug Song
1702: removed many bugs, re-added newer features and
1703: created OpenSSH.
1704: Markus Friedl contributed the support for SSH
1705: protocol versions 1.5 and 2.0.
![[BACK]](/icons/back.gif){kind=icon}
Return to ssh.1 CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / src / usr.bin / ssh