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. It is intended to replace
56 rlogin and rsh, and provide secure encrypted communications between
57 two untrusted hosts over an insecure network. X11 connections and
58 arbitrary TCP/IP ports can also be forwarded over the secure channel.
61 connects and logs into the specified
64 his/her identity to the remote machine using one of several methods.
66 First, if the machine the user logs in from is listed in
69 .Pa @sysconfdir@/shosts.equiv
70 on the remote machine, and the user names are
71 the same on both sides, the user is immediately permitted to log in.
76 exists in the user's home directory on the
77 remote machine and contains a line containing the name of the client
78 machine and the name of the user on that machine, the user is
79 permitted to log in. This form of authentication alone is normally not
80 allowed by the server because it is not secure.
82 The second (and primary) authentication method is the
86 method combined with RSA-based host authentication. It
87 means that if the login would be permitted by
90 .Pa /etc/hosts.equiv ,
92 .Pa @sysconfdir@/shosts.equiv ,
93 and if additionally the server can verify the client's
95 .Pa @sysconfdir@/ssh_known_hosts
97 .Pa $HOME/.ssh/known_hosts
100 section), only then login is
101 permitted. This authentication method closes security holes due to IP
102 spoofing, DNS spoofing and routing spoofing. [Note to the
104 .Pa /etc/hosts.equiv ,
106 and the rlogin/rsh protocol in general, are inherently insecure and should be
107 disabled if security is desired.]
109 As a third authentication method,
111 supports RSA based authentication.
112 The scheme is based on public-key cryptography: there are cryptosystems
113 where encryption and decryption are done using separate keys, and it
114 is not possible to derive the decryption key from the encryption key.
115 RSA is one such system. The idea is that each user creates a public/private
116 key pair for authentication purposes. The
117 server knows the public key, and only the user knows the private key.
119 .Pa $HOME/.ssh/authorized_keys
120 lists the public keys that are permitted for logging
121 in. When the user logs in, the
123 program tells the server which key pair it would like to use for
124 authentication. The server checks if this key is permitted, and if
125 so, sends the user (actually the
127 program running on behalf of the user) a challenge, a random number,
128 encrypted by the user's public key. The challenge can only be
129 decrypted using the proper private key. The user's client then decrypts the
130 challenge using the private key, proving that he/she knows the private
131 key but without disclosing it to the server.
134 implements the RSA authentication protocol automatically. The user
135 creates his/her RSA key pair by running
137 This stores the private key in
139 and the public key in
140 .Pa \&.ssh/identity.pub
141 in the user's home directory. The user should then
145 .Pa \&.ssh/authorized_keys
146 in his/her home directory on the remote machine (the
148 file corresponds to the conventional
150 file, and has one key
151 per line, though the lines can be very long). After this, the user
152 can log in without giving the password. RSA authentication is much
153 more secure than rhosts authentication.
155 The most convenient way to use RSA authentication may be with an
156 authentication agent. See
158 for more information.
160 If other authentication methods fail,
162 prompts the user for a password. The password is sent to the remote
163 host for checking; however, since all communications are encrypted,
164 the password cannot be seen by someone listening on the network.
166 When the user's identity has been accepted by the server, the server
167 either executes the given command, or logs into the machine and gives
168 the user a normal shell on the remote machine. All communication with
169 the remote command or shell will be automatically encrypted.
171 If a pseudo-terminal has been allocated (normal login session), the
172 user can disconnect with
178 All forwarded connections can be listed with
181 the session blocks waiting for forwarded X11 or TCP/IP
182 connections to terminate, it can be backgrounded with
184 (this should not be used while the user shell is active, as it can cause the
185 shell to hang). All available escapes can be listed with
188 A single tilde character can be sent as
190 (or by following the tilde by a character other than those described above).
191 The escape character must always follow a newline to be interpreted as
192 special. The escape character can be changed in configuration files
193 or on the command line.
195 If no pseudo tty has been allocated, the
196 session is transparent and can be used to reliably transfer binary
197 data. On most systems, setting the escape character to
199 will also make the session transparent even if a tty is used.
201 The session terminates when the command or shell in on the remote
202 machine exists and all X11 and TCP/IP connections have been closed.
203 The exit status of the remote program is returned as the exit status
207 If the user is using X11 (the
209 environment variable is set), the connection to the X11 display is
210 automatically forwarded to the remote side in such a way that any X11
211 programs started from the shell (or command) will go through the
212 encrypted channel, and the connection to the real X server will be made
213 from the local machine. The user should not manually set
215 Forwarding of X11 connections can be
216 configured on the command line or in configuration files.
222 will point to the server machine, but with a display number greater
223 than zero. This is normal, and happens because
227 X server on the server machine for forwarding the
228 connections over the encrypted channel.
231 will also automatically set up Xauthority data on the server machine.
232 For this purpose, it will generate a random authorization cookie,
233 store it in Xauthority on the server, and verify that any forwarded
234 connections carry this cookie and replace it by the real cookie when
235 the connection is opened. The real authentication cookie is never
236 sent to the server machine (and no cookies are sent in the plain).
238 If the user is using an authentication agent, the connection to the agent
239 is automatically forwarded to the remote side unless disabled on
240 command line or in a configuration file.
242 Forwarding of arbitrary TCP/IP connections over the secure channel can
243 be specified either on command line or in a configuration file. One
244 possible application of TCP/IP forwarding is a secure connection to an
245 electronic purse; another is going trough firewalls.
248 automatically maintains and checks a database containing RSA-based
249 identifications for all hosts it has ever been used with. The
250 database is stored in
251 .Pa \&.ssh/known_hosts
252 in the user's home directory. Additionally, the file
253 .Pa @sysconfdir@/ssh_known_hosts
254 is automatically checked for known hosts. Any new hosts are
255 automatically added to the user's file. If a host's identification
258 warns about this and disables password authentication to prevent a
259 trojan horse from getting the user's password. Another purpose of
260 this mechanism is to prevent man-in-the-middle attacks which could
261 otherwise be used to circumvent the encryption. The
262 .Cm StrictHostKeyChecking
263 option (see below) can be used to prevent logins to machines whose
264 host key is not known or has changed.
268 Disables forwarding of the authentication agent connection. This may
269 also be specified on a per-host basis in the configuration file.
270 .It Fl c Ar blowfish|3des
271 Selects the cipher to use for encrypting the session.
273 is used by default. It is believed to be secure.
275 (triple-des) is an encrypt-decrypt-encrypt triple with three different keys.
276 It is presumably more secure than the
278 cipher which is no longer supported in ssh.
280 is a fast block cipher, it appears very secure and is much faster than
282 .It Fl e Ar ch|^ch|none
283 Sets the escape character for sessions with a pty (default:
285 The escape character is only recognized at the beginning of a line. The
286 escape character followed by a dot
288 closes the connection, followed
289 by control-Z suspends the connection, and followed by itself sends the
290 escape character once. Setting the character to
292 disables any escapes and makes the session fully transparent.
296 to go to background just before command execution. This is useful
299 is going to ask for passwords or passphrases, but the user
300 wants it in the background. This implies
302 The recommended way to start X11 programs at a remote site is with
304 .Ic ssh -f host xterm .
305 .It Fl i Ar identity_file
306 Selects the file from which the identity (private key) for
307 RSA authentication is read. Default is
309 in the user's home directory. Identity files may also be specified on
310 a per-host basis in the configuration file. It is possible to have
313 options (and multiple identities specified in
314 configuration files).
316 Allows remote hosts to connect to local forwarded ports.
318 Disables forwarding of Kerberos tickets and AFS tokens. This may
319 also be specified on a per-host basis in the configuration file.
320 .It Fl l Ar login_name
321 Specifies the user to log in as on the remote machine. This may also
322 be specified on a per-host basis in the configuration file.
326 (actually, prevents reading from stdin).
327 This must be used when
329 is run in the background. A common trick is to use this to run X11
330 programs in a remote machine. For example,
331 .Ic ssh -n shadows.cs.hut.fi emacs &
332 will start an emacs on shadows.cs.hut.fi, and the X11
333 connection will be automatically forwarded over an encrypted channel.
336 program will be put in the background.
337 (This does not work if
339 needs to ask for a password or passphrase; see also the
343 Can be used to give options in the format used in the config file.
344 This is useful for specifying options for which there is no separate
345 command-line flag. The option has the same format as a line in the
348 Port to connect to on the remote host. This can be specified on a
349 per-host basis in the configuration file.
351 Use a non-privileged port for outgoing connections.
352 This can be used if your firewall does
353 not permit connections from privileged ports.
354 Note that this option turns off
355 .Cm RhostsAuthentication
357 .Cm RhostsRSAAuthentication .
359 Quiet mode. Causes all warning and diagnostic messages to be
360 suppressed. Only fatal errors are displayed.
362 Force pseudo-tty allocation. This can be used to execute arbitary
363 screen-based programs on a remote machine, which can be very useful
364 e.g. when implementing menu services.
368 to print debugging messages about its progress. This is helpful in
369 debugging connection, authentication, and configuration problems.
370 The verbose mode is also used to display
372 challenges, if the user entered "s/key" as password.
374 Disables X11 forwarding. This can also be specified on a per-host
375 basis in a configuration file.
377 Enables X11 forwarding.
379 Requests compression of all data (including stdin, stdout, stderr, and
380 data for forwarded X11 and TCP/IP connections). The compression
381 algorithm is the same used by gzip, and the
383 can be controlled by the
385 option (see below). Compression is desirable on modem lines and other
386 slow connections, but will only slow down things on fast networks.
387 The default value can be set on a host-by-host basis in the
388 configuration files; see the
391 .It Fl L Ar port:host:hostport
392 Specifies that the given port on the local (client) host is to be
393 forwarded to the given host and port on the remote side. This works
394 by allocating a socket to listen to
396 on the local side, and whenever a connection is made to this port, the
397 connection is forwarded over the secure channel, and a connection is
402 from the remote machine. Port forwardings can also be specified in the
403 configuration file. Only root can forward privileged ports.
404 IPv6 addresses can be specified with an alternative syntax:
405 .Ar port/host/hostport
406 .It Fl R Ar port:host:hostport
407 Specifies that the given port on the remote (server) host is to be
408 forwarded to the given host and port on the local side. This works
409 by allocating a socket to listen to
411 on the remote side, and whenever a connection is made to this port, the
412 connection is forwarded over the secure channel, and a connection is
417 from the local machine. Port forwardings can also be specified in the
418 configuration file. Privileged ports can be forwarded only when
419 logging in as root on the remote machine.
423 to use IPv4 addresses only.
427 to use IPv6 addresses only.
429 .Sh CONFIGURATION FILES
431 obtains configuration data from the following sources (in this order):
432 command line options, user's configuration file
433 .Pq Pa $HOME/.ssh/config ,
434 and system-wide configuration file
435 .Pq Pa @sysconfdir@/ssh_config .
436 For each parameter, the first obtained value
437 will be used. The configuration files contain sections bracketed by
438 "Host" specifications, and that section is only applied for hosts that
439 match one of the patterns given in the specification. The matched
440 host name is the one given on the command line.
442 Since the first obtained value for each parameter is used, more
443 host-specific declarations should be given near the beginning of the
444 file, and general defaults at the end.
446 The configuration file has the following format:
448 Empty lines and lines starting with
452 Otherwise a line is of the format
453 .Dq keyword arguments .
455 keywords and their meanings are as follows (note that the
456 configuration files are case-sensitive):
459 Restricts the following declarations (up to the next
461 keyword) to be only for those hosts that match one of the patterns
462 given after the keyword.
466 can be used as wildcards in the
469 as a pattern can be used to provide global
470 defaults for all hosts. The host is the
472 argument given on the command line (i.e., the name is not converted to
473 a canonicalized host name before matching).
474 .It Cm AFSTokenPassing
475 Specifies whether to pass AFS tokens to remote host. The argument to
483 passphrase/password querying will be disabled. This
484 option is useful in scripts and other batch jobs where you have no
485 user to supply the password. The argument must be
490 Specifies the cipher to use for encrypting the session. Currently,
494 are supported. The default is
497 Specifies whether to use compression. The argument must be
501 .It Cm CompressionLevel
502 Specifies the compression level to use if compression is enable. The
503 argument must be an integer from 1 (fast) to 9 (slow, best). The
504 default level is 6, which is good for most applications. The meaning
505 of the values is the same as in GNU GZIP.
506 .It Cm ConnectionAttempts
507 Specifies the number of tries (one per second) to make before falling
508 back to rsh or exiting. The argument must be an integer. This may be
509 useful in scripts if the connection sometimes fails.
511 Sets the escape character (default:
513 The escape character can also
514 be set on the command line. The argument should be a single
517 followed by a letter, or
519 to disable the escape
520 character entirely (making the connection transparent for binary
523 Specifies that if connecting via
525 fails due to a connection refused error (there is no
527 listening on the remote host),
529 should automatically be used instead (after a suitable warning about
530 the session being unencrypted). The argument must be
535 Specifies whether the connection to the authentication agent (if any)
536 will be forwarded to the remote machine. The argument must be
541 Specifies whether X11 connections will be automatically redirected
542 over the secure channel and
544 set. The argument must be
549 Specifies whether remote hosts are allowed to connect to local
557 .It Cm GlobalKnownHostsFile
558 Specifies a file to use instead of
559 .Pa @sysconfdir@/ssh_known_hosts .
561 Specifies the real host name to log into. This can be used to specify
562 nicnames or abbreviations for hosts. Default is the name given on the
563 command line. Numeric IP addresses are also permitted (both on the
568 Specifies the file from which the user's RSA authentication identity
571 in the user's home directory).
572 Additionally, any identities represented by the authentication agent
573 will be used for authentication. The file name may use the tilde
574 syntax to refer to a user's home directory. It is possible to have
575 multiple identity files specified in configuration files; all these
576 identities will be tried in sequence.
578 Specifies whether the system should send keepalive messages to the
579 other side. If they are sent, death of the connection or crash of one
580 of the machines will be properly noticed. However, this means that
581 connections will die if the route is down temporarily, and some people
586 (to send keepalives), and the client will notice
587 if the network goes down or the remote host dies. This is important
588 in scripts, and many users want it too.
590 To disable keepalives, the value should be set to
592 in both the server and the client configuration files.
593 .It Cm KerberosAuthentication
594 Specifies whether Kerberos authentication will be used. The argument to
599 .It Cm KerberosTgtPassing
600 Specifies whether a Kerberos TGT will be forwarded to the server. This
601 will only work if the Kerberos server is actually an AFS kaserver. The
602 argument to this keyword must be
607 Specifies that a TCP/IP port on the local machine be forwarded over
608 the secure channel to given host:port from the remote machine. The
609 first argument must be a port number, and the second must be
610 host:port. Multiple forwardings may be specified, and additional
611 forwardings can be given on the command line. Only the root can
612 forward privileged ports.
613 .It Cm PasswordAuthentication
614 Specifies whether to use password authentication. The argument to
620 Gives the verbosity level that is used when logging messages from
622 The possible values are:
623 QUIET, FATAL, ERROR, INFO, CHAT and DEBUG.
625 .It Cm NumberOfPasswordPrompts
626 Specifies the number of password prompts before giving up. The
627 argument to this keyword must be an integer. Default is 3.
629 Specifies the port number to connect on the remote host. Default is
632 Specifies the command to use to connect to the server. The command
633 string extends to the end of the line, and is executed with /bin/sh.
634 In the command string, %h will be substituted by the host name to
635 connect and %p by the port. The command can be basically anything,
636 and should read from its stdin and write to its stdout. It should
637 eventually connect an
639 server running on some machine, or execute
641 somewhere. Host key management will be done using the
642 HostName of the host being connected (defaulting to the name typed by
646 is not available for connects with a proxy command.
649 Specifies that a TCP/IP port on the remote machine be forwarded over
650 the secure channel to given host:port from the local machine. The
651 first argument must be a port number, and the second must be
652 host:port. Multiple forwardings may be specified, and additional
653 forwardings can be given on the command line. Only the root can
654 forward privileged ports.
655 .It Cm RhostsAuthentication
656 Specifies whether to try rhosts based authentication. Note that this
657 declaration only affects the client side and has no effect whatsoever
658 on security. Disabling rhosts authentication may reduce
659 authentication time on slow connections when rhosts authentication is
660 not used. Most servers do not permit RhostsAuthentication because it
661 is not secure (see RhostsRSAAuthentication). The argument to this
666 .It Cm RhostsRSAAuthentication
667 Specifies whether to try rhosts based authentication with RSA host
668 authentication. This is the primary authentication method for most
669 sites. The argument must be
673 .It Cm RSAAuthentication
674 Specifies whether to try RSA authentication. The argument to this
679 RSA authentication will only be
680 attempted if the identity file exists, or an authentication agent is
682 .It Cm SkeyAuthentication
683 Specifies whether to use
685 authentication. The argument to
693 If this flag is set to
695 ssh will additionally check the host ip address in the
697 file. This allows ssh to detect if a host key changed due to DNS spoofing.
698 If the option is set to
700 the check will not be executed.
701 .It Cm StrictHostKeyChecking
702 If this flag is set to
705 ssh will never automatically add host keys to the
706 .Pa $HOME/.ssh/known_hosts
707 file, and refuses to connect hosts whose host key has changed. This
708 provides maximum protection against trojan horse attacks. However, it
709 can be somewhat annoying if you don't have good
710 .Pa @sysconfdir@/ssh_known_hosts
711 files installed and frequently
712 connect new hosts. Basically this option forces the user to manually
713 add any new hosts. Normally this option is disabled, and new hosts
714 will automatically be added to the known host files. The host keys of
715 known hosts will be verified automatically in either case. The
721 Specifies the user to log in as. This can be useful if you have a
722 different user name in different machines. This saves the trouble of
723 having to remember to give the user name on the command line.
724 .It Cm UserKnownHostsFile
725 Specifies a file to use instead of
726 .Pa $HOME/.ssh/known_hosts .
727 .It Cm UsePrivilegedPort
728 Specifies whether to use a privileged port for outgoing connections.
735 Note that setting this option to
738 .Cm RhostsAuthentication
740 .Cm RhostsRSAAuthentication .
742 Specifies that rlogin/rsh should be used for this host. It is
743 possible that the host does not at all support the
745 protocol. This causes
749 All other options (except
751 are ignored if this has been specified. The argument must be
757 will normally set the following environment variables:
762 variable indicates the location of the X11 server. It is
765 to point to a value of the form
767 where hostname indicates
768 the host where the shell runs, and n is an integer >= 1. Ssh uses
769 this special value to forward X11 connections over the secure
770 channel. The user should normally not set DISPLAY explicitly, as that
771 will render the X11 connection insecure (and will require the user to
772 manually copy any required authorization cookies).
774 Set to the path of the user's home directory.
778 set for compatibility with systems that use this variable.
780 Set to point the user's mailbox.
784 as specified when compiling
787 indicates the path of a unix-domain socket used to communicate with the
790 Identifies the client end of the connection. The variable contains
791 three space-separated values: client ip-address, client port number,
792 and server port number.
794 This is set to the name of the tty (path to the device) associated
795 with the current shell or command. If the current session has no tty,
796 this variable is not set.
798 The timezone variable is set to indicate the present timezone if it
799 was set when the daemon was started (e.i., the daemon passes the value
800 on to new connections).
802 Set to the name of the user logging in.
808 .Pa $HOME/.ssh/environment ,
809 and adds lines of the format
813 .Bl -tag -width $HOME/.ssh/known_hosts
814 .It Pa $HOME/.ssh/known_hosts
815 Records host keys for all hosts the user has logged into (that are not
817 .Pa @sysconfdir@/ssh_known_hosts ) .
820 .It Pa $HOME/.ssh/identity
821 Contains the RSA authentication identity of the user. This file
822 contains sensitive data and should be readable by the user but not
823 accessible by others (read/write/execute).
826 ignores this file if it is accessible by others.
827 It is possible to specify a passphrase when
828 generating the key; the passphrase will be used to encrypt the
829 sensitive part of this file using 3DES.
830 .It Pa $HOME/.ssh/identity.pub
831 Contains the public key for authentication (public part of the
832 identity file in human-readable form). The contents of this file
834 .Pa $HOME/.ssh/authorized_keys
836 where you wish to log in using RSA authentication. This file is not
837 sensitive and can (but need not) be readable by anyone. This file is
838 never used automatically and is not necessary; it is only provided for
839 the convenience of the user.
840 .It Pa $HOME/.ssh/config
841 This is the per-user configuration file. The format of this file is
842 described above. This file is used by the
844 client. This file does not usually contain any sensitive information,
845 but the recommended permissions are read/write for the user, and not
846 accessible by others.
847 .It Pa $HOME/.ssh/authorized_keys
848 Lists the RSA keys that can be used for logging in as this user. The
849 format of this file is described in the
851 manual page. In the simplest form the format is the same as the .pub
852 identity files (that is, each line contains the number of bits in
853 modulus, public exponent, modulus, and comment fields, separated by
854 spaces). This file is not highly sensitive, but the recommended
855 permissions are read/write for the user, and not accessible by others.
856 .It Pa @sysconfdir@/ssh_known_hosts
857 Systemwide list of known host keys. This file should be prepared by the
858 system administrator to contain the public host keys of all machines in the
859 organization. This file should be world-readable. This file contains
860 public keys, one per line, in the following format (fields separated
861 by spaces): system name, number of bits in modulus, public exponent,
862 modulus, and optional comment field. When different names are used
863 for the same machine, all such names should be listed, separated by
864 commas. The format is described on the
868 The canonical system name (as returned by name servers) is used by
870 to verify the client host when logging in; other names are needed because
872 does not convert the user-supplied name to a canonical name before
873 checking the key, because someone with access to the name servers
874 would then be able to fool host authentication.
875 .It Pa @sysconfdir@/ssh_config
876 Systemwide configuration file. This file provides defaults for those
877 values that are not specified in the user's configuration file, and
878 for those users who do not have a configuration file. This file must
883 authentication to list the
884 host/user pairs that are permitted to log in. (Note that this file is
885 also used by rlogin and rsh, which makes using this file insecure.)
886 Each line of the file contains a host name (in the canonical form
887 returned by name servers), and then a user name on that host,
888 separated by a space. One some machines this file may need to be
889 world-readable if the user's home directory is on a NFS partition,
892 reads it as root. Additionally, this file must be owned by the user,
893 and must not have write permissions for anyone else. The recommended
894 permission for most machines is read/write for the user, and not
895 accessible by others.
899 will be installed so that it requires successful RSA host
900 authentication before permitting \s+2.\s0rhosts authentication. If your
901 server machine does not have the client's host key in
902 .Pa @sysconfdir@/ssh_known_hosts ,
904 .Pa $HOME/.ssh/known_hosts .
905 The easiest way to do this is to
906 connect back to the client from the server machine using ssh; this
907 will automatically add the host key inxi
908 .Pa $HOME/.ssh/known_hosts .
910 This file is used exactly the same way as
913 having this file is to be able to use rhosts authentication with
915 without permitting login with
919 .It Pa /etc/hosts.equiv
920 This file is used during
921 .Pa \&.rhosts authentication. It contains
922 canonical hosts names, one per line (the full format is described on
925 manual page). If the client host is found in this file, login is
926 automatically permitted provided client and server user names are the
927 same. Additionally, successful RSA host authentication is normally
928 required. This file should only be writable by root.
929 .It Pa @sysconfdir@/shosts.equiv
930 This file is processed exactly as
931 .Pa /etc/hosts.equiv .
932 This file may be useful to permit logins using
934 but not using rsh/rlogin.
935 .It Pa @sysconfdir@/sshrc
936 Commands in this file are executed by
938 when the user logs in just before the user's shell (or command) is started.
941 manual page for more information.
943 Commands in this file are executed by
945 when the user logs in just before the user's shell (or command) is
949 manual page for more information.
950 .It Pa $HOME/.ssh/environment
951 Contains additional definitions for environment variables, see section
954 .It Pa libcrypto.so.X.1
955 A version of this library which includes support for the RSA algorithm
956 is required for proper operation.
958 Tatu Ylonen <ylo@cs.hut.fi>
960 Issues can be found from the SSH WWW home page:
962 .Dl http://www.cs.hut.fi/ssh
965 is a derivative of the original (free) ssh 1.2.12 release, but with bugs
966 removed and newer features re-added. Rapidly after the 1.2.12 release,
967 newer versions bore successively more restrictive licenses. This version
971 has all components of a restrictive nature (ie. patents, see
973 directly removed from the source code; any licensed or patented components
977 has been updated to support ssh protocol 1.5.
979 contains added support for
981 authentication and ticket passing.
983 supports one-time password authentication with
987 The libraries described in
989 are required for proper operation.
991 OpenSSH has been created by Aaron Campbell, Bob Beck, Markus Friedl,
992 Niels Provos, Theo de Raadt, and Dug Song.
andersk / openssh.git / blob