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