5 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
7 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
8 .\" All rights reserved
10 .\" Created: Sat Apr 22 21:55:14 1995 ylo
14 .Dd September 25, 1999
19 .Nd OpenSSH secure shell client (remote login program)
22 .Op Fl l Ar login_name
23 .Op Ar hostname | user@hostname
28 .Op Fl c Ar blowfish | 3des
29 .Op Fl e Ar escape_char
30 .Op Fl i Ar identity_file
31 .Op Fl l Ar login_name
50 .Op Ar hostname | user@hostname
54 (Secure Shell) is a program for logging into a remote machine and for
55 executing commands on a remote machine.
56 It is intended to replace
57 rlogin and rsh, and provide secure encrypted communications between
58 two untrusted hosts over an insecure network.
60 arbitrary TCP/IP ports can also be forwarded over the secure channel.
63 connects and logs into the specified
66 his/her identity to the remote machine using one of several methods.
68 First, if the machine the user logs in from is listed in
72 on the remote machine, and the user names are
73 the same on both sides, the user is immediately permitted to log in.
78 exists in the user's home directory on the
79 remote machine and contains a line containing the name of the client
80 machine and the name of the user on that machine, the user is
82 This form of authentication alone is normally not
83 allowed by the server because it is not secure.
85 The second (and primary) authentication method is the
89 method combined with RSA-based host authentication.
90 It means that if the login would be permitted by
93 .Pa /etc/hosts.equiv ,
95 .Pa /etc/shosts.equiv ,
96 and if additionally the server can verify the client's
98 .Pa /etc/ssh_known_hosts
100 .Pa $HOME/.ssh/known_hosts
103 section), only then login is permitted.
104 This authentication method closes security holes due to IP
105 spoofing, DNS spoofing and routing spoofing.
106 [Note to the administrator:
107 .Pa /etc/hosts.equiv ,
109 and the rlogin/rsh protocol in general, are inherently insecure and should be
110 disabled if security is desired.]
112 As a third authentication method,
114 supports RSA based authentication.
115 The scheme is based on public-key cryptography: there are cryptosystems
116 where encryption and decryption are done using separate keys, and it
117 is not possible to derive the decryption key from the encryption key.
118 RSA is one such system.
119 The idea is that each user creates a public/private
120 key pair for authentication purposes.
121 The server knows the public key, and only the user knows the private key.
123 .Pa $HOME/.ssh/authorized_keys
124 lists the public keys that are permitted for logging
126 When the user logs in, the
128 program tells the server which key pair it would like to use for
130 The server checks if this key is permitted, and if
131 so, sends the user (actually the
133 program running on behalf of the user) a challenge, a random number,
134 encrypted by the user's public key.
135 The challenge can only be
136 decrypted using the proper private key.
137 The user's client then decrypts the
138 challenge using the private key, proving that he/she knows the private
139 key but without disclosing it to the server.
142 implements the RSA authentication protocol automatically.
143 The user creates his/her RSA key pair by running
145 This stores the private key in
147 and the public key in
148 .Pa \&.ssh/identity.pub
149 in the user's home directory.
150 The user should then copy the
153 .Pa \&.ssh/authorized_keys
154 in his/her home directory on the remote machine (the
156 file corresponds to the conventional
158 file, and has one key
159 per line, though the lines can be very long).
160 After this, the user can log in without giving the password.
161 RSA authentication is much
162 more secure than rhosts authentication.
164 The most convenient way to use RSA authentication may be with an
165 authentication agent.
168 for more information.
170 If other authentication methods fail,
172 prompts the user for a password.
173 The password is sent to the remote
174 host for checking; however, since all communications are encrypted,
175 the password cannot be seen by someone listening on the network.
177 When the user's identity has been accepted by the server, the server
178 either executes the given command, or logs into the machine and gives
179 the user a normal shell on the remote machine.
180 All communication with
181 the remote command or shell will be automatically encrypted.
183 If a pseudo-terminal has been allocated (normal login session), the
184 user can disconnect with
190 All forwarded connections can be listed with
193 the session blocks waiting for forwarded X11 or TCP/IP
194 connections to terminate, it can be backgrounded with
196 (this should not be used while the user shell is active, as it can cause the
198 All available escapes can be listed with
201 A single tilde character can be sent as
203 (or by following the tilde by a character other than those described above).
204 The escape character must always follow a newline to be interpreted as
206 The escape character can be changed in configuration files
207 or on the command line.
209 If no pseudo tty has been allocated, the
210 session is transparent and can be used to reliably transfer binary
212 On most systems, setting the escape character to
214 will also make the session transparent even if a tty is used.
216 The session terminates when the command or shell in on the remote
217 machine exists and all X11 and TCP/IP connections have been closed.
218 The exit status of the remote program is returned as the exit status
222 If the user is using X11 (the
224 environment variable is set), the connection to the X11 display is
225 automatically forwarded to the remote side in such a way that any X11
226 programs started from the shell (or command) will go through the
227 encrypted channel, and the connection to the real X server will be made
228 from the local machine.
229 The user should not manually set
231 Forwarding of X11 connections can be
232 configured on the command line or in configuration files.
238 will point to the server machine, but with a display number greater
240 This is normal, and happens because
244 X server on the server machine for forwarding the
245 connections over the encrypted channel.
248 will also automatically set up Xauthority data on the server machine.
249 For this purpose, it will generate a random authorization cookie,
250 store it in Xauthority on the server, and verify that any forwarded
251 connections carry this cookie and replace it by the real cookie when
252 the connection is opened.
253 The real authentication cookie is never
254 sent to the server machine (and no cookies are sent in the plain).
256 If the user is using an authentication agent, the connection to the agent
257 is automatically forwarded to the remote side unless disabled on
258 command line or in a configuration file.
260 Forwarding of arbitrary TCP/IP connections over the secure channel can
261 be specified either on command line or in a configuration file.
262 One possible application of TCP/IP forwarding is a secure connection to an
263 electronic purse; another is going trough firewalls.
266 automatically maintains and checks a database containing RSA-based
267 identifications for all hosts it has ever been used with.
268 The database is stored in
269 .Pa \&.ssh/known_hosts
270 in the user's home directory.
271 Additionally, the file
272 .Pa /etc/ssh_known_hosts
273 is automatically checked for known hosts.
274 Any new hosts are automatically added to the user's file.
275 If a host's identification
278 warns about this and disables password authentication to prevent a
279 trojan horse from getting the user's password.
281 this mechanism is to prevent man-in-the-middle attacks which could
282 otherwise be used to circumvent the encryption.
284 .Cm StrictHostKeyChecking
285 option (see below) can be used to prevent logins to machines whose
286 host key is not known or has changed.
290 Disables forwarding of the authentication agent connection. This may
291 also be specified on a per-host basis in the configuration file.
292 .It Fl c Ar blowfish|3des
293 Selects the cipher to use for encrypting the session.
296 It is believed to be secure.
298 (triple-des) is an encrypt-decrypt-encrypt triple with three different keys.
299 It is presumably more secure than the
301 cipher which is no longer supported in ssh.
303 is a fast block cipher, it appears very secure and is much faster than
305 .It Fl e Ar ch|^ch|none
306 Sets the escape character for sessions with a pty (default:
308 The escape character is only recognized at the beginning of a line.
309 The escape character followed by a dot
311 closes the connection, followed
312 by control-Z suspends the connection, and followed by itself sends the
313 escape character once.
314 Setting the character to
316 disables any escapes and makes the session fully transparent.
320 to go to background just before command execution.
323 is going to ask for passwords or passphrases, but the user
324 wants it in the background.
327 The recommended way to start X11 programs at a remote site is with
329 .Ic ssh -f host xterm .
331 Allows remote hosts to connect to local forwarded ports.
332 .It Fl i Ar identity_file
333 Selects the file from which the identity (private key) for
334 RSA authentication is read.
337 in the user's home directory.
338 Identity files may also be specified on
339 a per-host basis in the configuration file.
340 It is possible to have multiple
342 options (and multiple identities specified in
343 configuration files).
345 Disables forwarding of Kerberos tickets and AFS tokens. This may
346 also be specified on a per-host basis in the configuration file.
347 .It Fl l Ar login_name
348 Specifies the user to log in as on the remote machine.
349 This also may be specified on a per-host basis in the configuration file.
353 (actually, prevents reading from stdin).
354 This must be used when
356 is run in the background.
357 A common trick is to use this to run X11 programs on a remote machine.
359 .Ic ssh -n shadows.cs.hut.fi emacs &
360 will start an emacs on shadows.cs.hut.fi, and the X11
361 connection will be automatically forwarded over an encrypted channel.
364 program will be put in the background.
365 (This does not work if
367 needs to ask for a password or passphrase; see also the
371 Can be used to give options in the format used in the config file.
372 This is useful for specifying options for which there is no separate
374 The option has the same format as a line in the configuration file.
376 Port to connect to on the remote host.
377 This can be specified on a
378 per-host basis in the configuration file.
380 Use a non-privileged port for outgoing connections.
381 This can be used if your firewall does
382 not permit connections from privileged ports.
383 Note that this option turns off
384 .Cm RhostsAuthentication
386 .Cm RhostsRSAAuthentication .
389 Causes all warning and diagnostic messages to be suppressed.
390 Only fatal errors are displayed.
392 Force pseudo-tty allocation.
393 This can be used to execute arbitary
394 screen-based programs on a remote machine, which can be very useful,
395 e.g., when implementing menu services.
400 to print debugging messages about its progress.
402 debugging connection, authentication, and configuration problems.
403 The verbose mode is also used to display
405 challenges, if the user entered "s/key" as password.
407 Disables X11 forwarding.
408 This can also be specified on a per-host basis in a configuration file.
410 Enables X11 forwarding.
412 Requests compression of all data (including stdin, stdout, stderr, and
413 data for forwarded X11 and TCP/IP connections).
414 The compression algorithm is the same used by
418 can be controlled by the
421 Compression is desirable on modem lines and other
422 slow connections, but will only slow down things on fast networks.
423 The default value can be set on a host-by-host basis in the
424 configuration files; see the
427 .It Fl L Ar port:host:hostport
428 Specifies that the given port on the local (client) host is to be
429 forwarded to the given host and port on the remote side.
430 This works by allocating a socket to listen to
432 on the local side, and whenever a connection is made to this port, the
433 connection is forwarded over the secure channel, and a connection is
438 from the remote machine.
439 Port forwardings can also be specified in the configuration file.
440 Only root can forward privileged ports.
441 IPv6 addresses can be specified with an alternative syntax:
442 .Ar port/host/hostport
443 .It Fl R Ar port:host:hostport
444 Specifies that the given port on the remote (server) host is to be
445 forwarded to the given host and port on the local side.
446 This works by allocating a socket to listen to
448 on the remote side, and whenever a connection is made to this port, the
449 connection is forwarded over the secure channel, and a connection is
454 from the local machine.
455 Port forwardings can also be specified in the configuration file.
456 Privileged ports can be forwarded only when
457 logging in as root on the remote machine.
461 to use IPv4 addresses only.
465 to use IPv6 addresses only.
467 .Sh CONFIGURATION FILES
469 obtains configuration data from the following sources (in this order):
470 command line options, user's configuration file
471 .Pq Pa $HOME/.ssh/config ,
472 and system-wide configuration file
473 .Pq Pa /etc/ssh_config .
474 For each parameter, the first obtained value
476 The configuration files contain sections bracketed by
478 specifications, and that section is only applied for hosts that
479 match one of the patterns given in the specification.
480 The matched host name is the one given on the command line.
482 Since the first obtained value for each parameter is used, more
483 host-specific declarations should be given near the beginning of the
484 file, and general defaults at the end.
486 The configuration file has the following format:
488 Empty lines and lines starting with
492 Otherwise a line is of the format
493 .Dq keyword arguments .
495 keywords and their meanings are as follows (note that the
496 configuration files are case-sensitive):
499 Restricts the following declarations (up to the next
501 keyword) to be only for those hosts that match one of the patterns
502 given after the keyword.
506 can be used as wildcards in the
510 as a pattern can be used to provide global
511 defaults for all hosts.
514 argument given on the command line (i.e., the name is not converted to
515 a canonicalized host name before matching).
516 .It Cm AFSTokenPassing
517 Specifies whether to pass AFS tokens to remote host. The argument to
525 passphrase/password querying will be disabled.
526 This option is useful in scripts and other batch jobs where you have no
527 user to supply the password.
533 If this flag is set to
535 ssh will additionally check the host ip address in the
537 file. This allows ssh to detect if a host key changed due to DNS spoofing.
538 If the option is set to
540 the check will not be executed.
542 Specifies the cipher to use for encrypting the session.
551 Specifies whether to use compression.
556 .It Cm CompressionLevel
557 Specifies the compression level to use if compression is enable.
558 The argument must be an integer from 1 (fast) to 9 (slow, best).
559 The default level is 6, which is good for most applications.
560 The meaning of the values is the same as in
562 .It Cm ConnectionAttempts
563 Specifies the number of tries (one per second) to make before falling
564 back to rsh or exiting.
565 The argument must be an integer.
566 This may be useful in scripts if the connection sometimes fails.
568 Sets the escape character (default:
570 The escape character can also
571 be set on the command line.
572 The argument should be a single character,
574 followed by a letter, or
576 to disable the escape
577 character entirely (making the connection transparent for binary
580 Specifies that if connecting via
582 fails due to a connection refused error (there is no
584 listening on the remote host),
586 should automatically be used instead (after a suitable warning about
587 the session being unencrypted).
593 Specifies whether the connection to the authentication agent (if any)
594 will be forwarded to the remote machine.
600 Specifies whether X11 connections will be automatically redirected
601 over the secure channel and
611 Specifies whether remote hosts are allowed to connect to local
619 .It Cm GlobalKnownHostsFile
620 Specifies a file to use instead of
621 .Pa /etc/ssh_known_hosts .
623 Specifies the real host name to log into.
624 This can be used to specify nicknames or abbreviations for hosts.
625 Default is the name given on the command line.
626 Numeric IP addresses are also permitted (both on the command line and in
630 Specifies the file from which the user's RSA authentication identity
633 in the user's home directory).
634 Additionally, any identities represented by the authentication agent
635 will be used for authentication.
636 The file name may use the tilde
637 syntax to refer to a user's home directory.
638 It is possible to have
639 multiple identity files specified in configuration files; all these
640 identities will be tried in sequence.
642 Specifies whether the system should send keepalive messages to the
644 If they are sent, death of the connection or crash of one
645 of the machines will be properly noticed.
646 However, this means that
647 connections will die if the route is down temporarily, and some people
652 (to send keepalives), and the client will notice
653 if the network goes down or the remote host dies.
654 This is important in scripts, and many users want it too.
656 To disable keepalives, the value should be set to
658 in both the server and the client configuration files.
659 .It Cm KerberosAuthentication
660 Specifies whether Kerberos authentication will be used. The argument to
665 .It Cm KerberosTgtPassing
666 Specifies whether a Kerberos TGT will be forwarded to the server. This
667 will only work if the Kerberos server is actually an AFS kaserver. The
668 argument to this keyword must be
673 Specifies that a TCP/IP port on the local machine be forwarded over
674 the secure channel to given host:port from the remote machine.
675 The first argument must be a port number, and the second must be
677 Multiple forwardings may be specified, and additional
678 forwardings can be given on the command line.
679 Only the superuser can forward privileged ports.
681 Gives the verbosity level that is used when logging messages from
683 The possible values are:
684 QUIET, FATAL, ERROR, INFO, VERBOSE and DEBUG.
686 .It Cm NumberOfPasswordPrompts
687 Specifies the number of password prompts before giving up. The
688 argument to this keyword must be an integer. Default is 3.
689 .It Cm PasswordAuthentication
690 Specifies whether to use password authentication.
691 The argument to this keyword must be
696 Specifies the port number to connect on the remote host.
699 Specifies the command to use to connect to the server.
701 string extends to the end of the line, and is executed with
703 In the command string,
705 will be substituted by the host name to
709 The command can be basically anything,
710 and should read from its standard input and write to its standard output.
711 It should eventually connect an
713 server running on some machine, or execute
716 Host key management will be done using the
717 HostName of the host being connected (defaulting to the name typed by
721 is not available for connects with a proxy command.
724 Specifies that a TCP/IP port on the remote machine be forwarded over
725 the secure channel to given host:port from the local machine.
726 The first argument must be a port number, and the second must be
728 Multiple forwardings may be specified, and additional
729 forwardings can be given on the command line.
730 Only the superuser can forward privileged ports.
731 .It Cm RhostsAuthentication
732 Specifies whether to try rhosts based authentication.
734 declaration only affects the client side and has no effect whatsoever
736 Disabling rhosts authentication may reduce
737 authentication time on slow connections when rhosts authentication is
739 Most servers do not permit RhostsAuthentication because it
740 is not secure (see RhostsRSAAuthentication).
741 The argument to this keyword must be
745 .It Cm RhostsRSAAuthentication
746 Specifies whether to try rhosts based authentication with RSA host
748 This is the primary authentication method for most sites.
753 .It Cm RSAAuthentication
754 Specifies whether to try RSA authentication.
755 The argument to this keyword must be
759 RSA authentication will only be
760 attempted if the identity file exists, or an authentication agent is
762 .It Cm SkeyAuthentication
763 Specifies whether to use
766 The argument to this keyword must be
772 .It Cm StrictHostKeyChecking
773 If this flag is set to
776 ssh will never automatically add host keys to the
777 .Pa $HOME/.ssh/known_hosts
778 file, and refuses to connect hosts whose host key has changed.
779 This provides maximum protection against trojan horse attacks.
780 However, it can be somewhat annoying if you don't have good
781 .Pa /etc/ssh_known_hosts
782 files installed and frequently
784 Basically this option forces the user to manually
786 Normally this option is disabled, and new hosts
787 will automatically be added to the known host files.
789 known hosts will be verified automatically in either case.
794 .It Cm UsePrivilegedPort
795 Specifies whether to use a privileged port for outgoing connections.
802 Note that setting this option to
805 .Cm RhostsAuthentication
807 .Cm RhostsRSAAuthentication .
809 Specifies the user to log in as.
810 This can be useful if you have a different user name on different machines.
811 This saves the trouble of
812 having to remember to give the user name on the command line.
813 .It Cm UserKnownHostsFile
814 Specifies a file to use instead of
815 .Pa $HOME/.ssh/known_hosts .
817 Specifies that rlogin/rsh should be used for this host.
818 It is possible that the host does not at all support the
823 to immediately execute
825 All other options (except
827 are ignored if this has been specified.
834 will normally set the following environment variables:
839 variable indicates the location of the X11 server.
840 It is automatically set by
842 to point to a value of the form
844 where hostname indicates
845 the host where the shell runs, and n is an integer >= 1.
847 uses this special value to forward X11 connections over the secure
849 The user should normally not set DISPLAY explicitly, as that
850 will render the X11 connection insecure (and will require the user to
851 manually copy any required authorization cookies).
853 Set to the path of the user's home directory.
857 set for compatibility with systems that use this variable.
859 Set to point the user's mailbox.
863 as specified when compiling
866 indicates the path of a unix-domain socket used to communicate with the
869 Identifies the client end of the connection.
870 The variable contains
871 three space-separated values: client ip-address, client port number,
872 and server port number.
874 This is set to the name of the tty (path to the device) associated
875 with the current shell or command.
876 If the current session has no tty,
877 this variable is not set.
879 The timezone variable is set to indicate the present timezone if it
880 was set when the daemon was started (e.i., the daemon passes the value
881 on to new connections).
883 Set to the name of the user logging in.
889 .Pa $HOME/.ssh/environment ,
890 and adds lines of the format
895 .It Pa $HOME/.ssh/known_hosts
896 Records host keys for all hosts the user has logged into (that are not
898 .Pa /etc/ssh_known_hosts ) .
901 .It Pa $HOME/.ssh/identity
902 Contains the RSA authentication identity of the user.
904 contains sensitive data and should be readable by the user but not
905 accessible by others (read/write/execute).
908 ignores this file if it is accessible by others.
909 It is possible to specify a passphrase when
910 generating the key; the passphrase will be used to encrypt the
911 sensitive part of this file using 3DES.
912 .It Pa $HOME/.ssh/identity.pub
913 Contains the public key for authentication (public part of the
914 identity file in human-readable form).
915 The contents of this file should be added to
916 .Pa $HOME/.ssh/authorized_keys
918 where you wish to log in using RSA authentication.
920 sensitive and can (but need not) be readable by anyone.
922 never used automatically and is not necessary; it is only provided for
923 the convenience of the user.
924 .It Pa $HOME/.ssh/config
925 This is the per-user configuration file.
926 The format of this file is described above.
927 This file is used by the
930 This file does not usually contain any sensitive information,
931 but the recommended permissions are read/write for the user, and not
932 accessible by others.
933 .It Pa $HOME/.ssh/authorized_keys
934 Lists the RSA keys that can be used for logging in as this user.
935 The format of this file is described in the
938 In the simplest form the format is the same as the .pub
939 identity files (that is, each line contains the number of bits in
940 modulus, public exponent, modulus, and comment fields, separated by
942 This file is not highly sensitive, but the recommended
943 permissions are read/write for the user, and not accessible by others.
944 .It Pa /etc/ssh_known_hosts
945 Systemwide list of known host keys.
946 This file should be prepared by the
947 system administrator to contain the public host keys of all machines in the
949 This file should be world-readable.
951 public keys, one per line, in the following format (fields separated
952 by spaces): system name, number of bits in modulus, public exponent,
953 modulus, and optional comment field.
954 When different names are used
955 for the same machine, all such names should be listed, separated by
957 The format is described on the
961 The canonical system name (as returned by name servers) is used by
963 to verify the client host when logging in; other names are needed because
965 does not convert the user-supplied name to a canonical name before
966 checking the key, because someone with access to the name servers
967 would then be able to fool host authentication.
968 .It Pa /etc/ssh_config
969 Systemwide configuration file.
970 This file provides defaults for those
971 values that are not specified in the user's configuration file, and
972 for those users who do not have a configuration file.
973 This file must be world-readable.
977 authentication to list the
978 host/user pairs that are permitted to log in.
979 (Note that this file is
980 also used by rlogin and rsh, which makes using this file insecure.)
981 Each line of the file contains a host name (in the canonical form
982 returned by name servers), and then a user name on that host,
983 separated by a space.
984 One some machines this file may need to be
985 world-readable if the user's home directory is on a NFS partition,
989 Additionally, this file must be owned by the user,
990 and must not have write permissions for anyone else.
992 permission for most machines is read/write for the user, and not
993 accessible by others.
997 will be installed so that it requires successful RSA host
998 authentication before permitting \s+2.\s0rhosts authentication.
999 If your server machine does not have the client's host key in
1000 .Pa /etc/ssh_known_hosts ,
1002 .Pa $HOME/.ssh/known_hosts .
1003 The easiest way to do this is to
1004 connect back to the client from the server machine using ssh; this
1005 will automatically add the host key inxi
1006 .Pa $HOME/.ssh/known_hosts .
1007 .It Pa $HOME/.shosts
1008 This file is used exactly the same way as
1011 having this file is to be able to use rhosts authentication with
1013 without permitting login with
1017 .It Pa /etc/hosts.equiv
1018 This file is used during
1019 .Pa \&.rhosts authentication.
1021 canonical hosts names, one per line (the full format is described on
1025 If the client host is found in this file, login is
1026 automatically permitted provided client and server user names are the
1028 Additionally, successful RSA host authentication is normally
1030 This file should only be writable by root.
1031 .It Pa /etc/shosts.equiv
1032 This file is processed exactly as
1033 .Pa /etc/hosts.equiv .
1034 This file may be useful to permit logins using
1036 but not using rsh/rlogin.
1038 Commands in this file are executed by
1040 when the user logs in just before the user's shell (or command) is started.
1043 manual page for more information.
1044 .It Pa $HOME/.ssh/rc
1045 Commands in this file are executed by
1047 when the user logs in just before the user's shell (or command) is
1051 manual page for more information.
1052 .It Pa $HOME/.ssh/environment
1053 Contains additional definitions for environment variables, see section
1056 .It Pa libcrypto.so.X.1
1057 A version of this library which includes support for the RSA algorithm
1058 is required for proper operation.
1061 is a derivative of the original (free) ssh 1.2.12 release by Tatu Ylonen,
1062 but with bugs removed and newer features re-added.
1064 1.2.12 release, newer versions of the original ssh bore successively
1065 more restrictive licenses, and thus demand for a free version was born.
1066 This version of OpenSSH
1069 has all components of a restrictive nature (i.e., patents, see
1071 directly removed from the source code; any licensed or patented components
1075 has been updated to support ssh protocol 1.5, making it compatible with
1076 all other ssh protocol 1 clients and servers.
1078 contains added support for
1080 authentication and ticket passing.
1082 supports one-time password authentication with
1086 The libraries described in
1088 are required for proper operation.
1090 OpenSSH has been created by Aaron Campbell, Bob Beck, Markus Friedl,
1091 Niels Provos, Theo de Raadt, and Dug Song.