3 .\" Author: Tatu Ylonen <ylo@cs.hut.fi>
4 .\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
5 .\" All rights reserved
7 .\" As far as I am concerned, the code I have written for this software
8 .\" can be used freely for any purpose. Any derived versions of this
9 .\" software must be clearly marked as such, and if the derived work is
10 .\" incompatible with the protocol description in the RFC file, it must be
11 .\" called by a name other than "ssh" or "Secure Shell".
13 .\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved.
14 .\" Copyright (c) 1999 Aaron Campbell. All rights reserved.
15 .\" Copyright (c) 1999 Theo de Raadt. All rights reserved.
17 .\" Redistribution and use in source and binary forms, with or without
18 .\" modification, are permitted provided that the following conditions
20 .\" 1. Redistributions of source code must retain the above copyright
21 .\" notice, this list of conditions and the following disclaimer.
22 .\" 2. Redistributions in binary form must reproduce the above copyright
23 .\" notice, this list of conditions and the following disclaimer in the
24 .\" documentation and/or other materials provided with the distribution.
26 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
27 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
28 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
29 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
30 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
31 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
32 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
33 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
34 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
35 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
37 .\" $OpenBSD: ssh.1,v 1.178 2003/10/11 08:24:08 markus Exp $
38 .Dd September 25, 1999
43 .Nd OpenSSH SSH client (remote login program)
46 .Op Fl 1246AaCfgkNnqsTtVvXxY
47 .Op Fl b Ar bind_address
48 .Op Fl c Ar cipher_spec
50 .Op Fl e Ar escape_char
51 .Op Fl F Ar configfile
52 .Op Fl i Ar identity_file
63 .Op Fl l Ar login_name
77 .Oo Ar user Ns @ Oc Ns Ar hostname
81 (SSH client) is a program for logging into a remote machine and for
82 executing commands on a remote machine.
83 It is intended to replace rlogin and rsh,
84 and provide secure encrypted communications between
85 two untrusted hosts over an insecure network.
86 X11 connections and arbitrary TCP/IP ports
87 can also be forwarded over the secure channel.
90 connects and logs into the specified
96 his/her identity to the remote machine using one of several methods
97 depending on the protocol version used.
103 is executed on the remote host instead of a login shell.
104 .Ss SSH protocol version 1
105 First, if the machine the user logs in from is listed in
108 .Pa /etc/shosts.equiv
109 on the remote machine, and the user names are
110 the same on both sides, the user is immediately permitted to log in.
115 exists in the user's home directory on the
116 remote machine and contains a line containing the name of the client
117 machine and the name of the user on that machine, the user is
119 This form of authentication alone is normally not
120 allowed by the server because it is not secure.
122 The second authentication method is the
126 method combined with RSA-based host authentication.
127 It means that if the login would be permitted by
130 .Pa /etc/hosts.equiv ,
132 .Pa /etc/shosts.equiv ,
133 and if additionally the server can verify the client's
135 .Pa /etc/ssh/ssh_known_hosts
137 .Pa $HOME/.ssh/known_hosts
140 section), only then is login permitted.
141 This authentication method closes security holes due to IP
142 spoofing, DNS spoofing and routing spoofing.
143 [Note to the administrator:
144 .Pa /etc/hosts.equiv ,
146 and the rlogin/rsh protocol in general, are inherently insecure and should be
147 disabled if security is desired.]
149 As a third authentication method,
151 supports RSA based authentication.
152 The scheme is based on public-key cryptography: there are cryptosystems
153 where encryption and decryption are done using separate keys, and it
154 is not possible to derive the decryption key from the encryption key.
155 RSA is one such system.
156 The idea is that each user creates a public/private
157 key pair for authentication purposes.
158 The server knows the public key, and only the user knows the private key.
161 .Pa $HOME/.ssh/authorized_keys
162 lists the public keys that are permitted for logging in.
163 When the user logs in, the
165 program tells the server which key pair it would like to use for
167 The server checks if this key is permitted, and if so,
168 sends the user (actually the
170 program running on behalf of the user) a challenge, a random number,
171 encrypted by the user's public key.
172 The challenge can only be decrypted using the proper private key.
173 The user's client then decrypts the challenge using the private key,
174 proving that he/she knows the private key
175 but without disclosing it to the server.
178 implements the RSA authentication protocol automatically.
179 The user creates his/her RSA key pair by running
181 This stores the private key in
182 .Pa $HOME/.ssh/identity
183 and stores the public key in
184 .Pa $HOME/.ssh/identity.pub
185 in the user's home directory.
186 The user should then copy the
189 .Pa $HOME/.ssh/authorized_keys
190 in his/her home directory on the remote machine (the
192 file corresponds to the conventional
194 file, and has one key
195 per line, though the lines can be very long).
196 After this, the user can log in without giving the password.
197 RSA authentication is much more secure than
201 The most convenient way to use RSA authentication may be with an
202 authentication agent.
205 for more information.
207 If other authentication methods fail,
209 prompts the user for a password.
210 The password is sent to the remote
211 host for checking; however, since all communications are encrypted,
212 the password cannot be seen by someone listening on the network.
213 .Ss SSH protocol version 2
214 When a user connects using protocol version 2,
215 similar authentication methods are available.
216 Using the default values for
217 .Cm PreferredAuthentications ,
218 the client will try to authenticate first using the hostbased method;
219 if this method fails, public key authentication is attempted,
220 and finally if this method fails, keyboard-interactive and
221 password authentication are tried.
223 The public key method is similar to RSA authentication described
224 in the previous section and allows the RSA or DSA algorithm to be used:
225 The client uses his private key,
226 .Pa $HOME/.ssh/id_dsa
228 .Pa $HOME/.ssh/id_rsa ,
229 to sign the session identifier and sends the result to the server.
230 The server checks whether the matching public key is listed in
231 .Pa $HOME/.ssh/authorized_keys
232 and grants access if both the key is found and the signature is correct.
233 The session identifier is derived from a shared Diffie-Hellman value
234 and is only known to the client and the server.
236 If public key authentication fails or is not available, a password
237 can be sent encrypted to the remote host to prove the user's identity.
241 supports hostbased or challenge response authentication.
243 Protocol 2 provides additional mechanisms for confidentiality
244 (the traffic is encrypted using 3DES, Blowfish, CAST128 or Arcfour)
245 and integrity (hmac-md5, hmac-sha1).
246 Note that protocol 1 lacks a strong mechanism for ensuring the
247 integrity of the connection.
248 .Ss Login session and remote execution
249 When the user's identity has been accepted by the server, the server
250 either executes the given command, or logs into the machine and gives
251 the user a normal shell on the remote machine.
252 All communication with
253 the remote command or shell will be automatically encrypted.
255 If a pseudo-terminal has been allocated (normal login session), the
256 user may use the escape characters noted below.
258 If no pseudo-tty has been allocated,
259 the session is transparent and can be used to reliably transfer binary data.
260 On most systems, setting the escape character to
262 will also make the session transparent even if a tty is used.
264 The session terminates when the command or shell on the remote
265 machine exits and all X11 and TCP/IP connections have been closed.
266 The exit status of the remote program is returned as the exit status of
268 .Ss Escape Characters
269 When a pseudo-terminal has been requested,
271 supports a number of functions through the use of an escape character.
273 A single tilde character can be sent as
275 or by following the tilde by a character other than those described below.
276 The escape character must always follow a newline to be interpreted as
278 The escape character can be changed in configuration files using the
280 configuration directive or on the command line by the
284 The supported escapes (assuming the default
294 List forwarded connections.
298 at logout when waiting for forwarded connection / X11 sessions to terminate.
300 Display a list of escape characters.
302 Send a BREAK to the remote system
303 (only useful for SSH protocol version 2 and if the peer supports it).
305 Open command line (only useful for adding port forwardings using the
311 Request rekeying of the connection
312 (only useful for SSH protocol version 2 and if the peer supports it).
314 .Ss X11 and TCP forwarding
319 (or see the description of the
323 options described later)
324 and the user is using X11 (the
326 environment variable is set), the connection to the X11 display is
327 automatically forwarded to the remote side in such a way that any X11
328 programs started from the shell (or command) will go through the
329 encrypted channel, and the connection to the real X server will be made
330 from the local machine.
331 The user should not manually set
333 Forwarding of X11 connections can be
334 configured on the command line or in configuration files.
340 will point to the server machine, but with a display number greater than zero.
341 This is normal, and happens because
345 X server on the server machine for forwarding the
346 connections over the encrypted channel.
349 will also automatically set up Xauthority data on the server machine.
350 For this purpose, it will generate a random authorization cookie,
351 store it in Xauthority on the server, and verify that any forwarded
352 connections carry this cookie and replace it by the real cookie when
353 the connection is opened.
354 The real authentication cookie is never
355 sent to the server machine (and no cookies are sent in the plain).
361 (or see the description of the
365 options described later) and
366 the user is using an authentication agent, the connection to the agent
367 is automatically forwarded to the remote side.
369 Forwarding of arbitrary TCP/IP connections over the secure channel can
370 be specified either on the command line or in a configuration file.
371 One possible application of TCP/IP forwarding is a secure connection to an
372 electronic purse; another is going through firewalls.
373 .Ss Server authentication
375 automatically maintains and checks a database containing
376 identifications for all hosts it has ever been used with.
377 Host keys are stored in
378 .Pa $HOME/.ssh/known_hosts
379 in the user's home directory.
380 Additionally, the file
381 .Pa /etc/ssh/ssh_known_hosts
382 is automatically checked for known hosts.
383 Any new hosts are automatically added to the user's file.
384 If a host's identification ever changes,
386 warns about this and disables password authentication to prevent a
387 trojan horse from getting the user's password.
388 Another purpose of this mechanism is to prevent man-in-the-middle attacks
389 which could otherwise be used to circumvent the encryption.
391 .Cm StrictHostKeyChecking
392 option can be used to prevent logins to machines whose
393 host key is not known or has changed.
395 The options are as follows:
400 to try protocol version 1 only.
404 to try protocol version 2 only.
408 to use IPv4 addresses only.
412 to use IPv6 addresses only.
414 Enables forwarding of the authentication agent connection.
415 This can also be specified on a per-host basis in a configuration file.
417 Agent forwarding should be enabled with caution.
418 Users with the ability to bypass file permissions on the remote host
419 (for the agent's Unix-domain socket)
420 can access the local agent through the forwarded connection.
421 An attacker cannot obtain key material from the agent,
422 however they can perform operations on the keys that enable them to
423 authenticate using the identities loaded into the agent.
425 Disables forwarding of the authentication agent connection.
426 .It Fl b Ar bind_address
427 Specify the interface to transmit from on machines with multiple
428 interfaces or aliased addresses.
430 Requests compression of all data (including stdin, stdout, stderr, and
431 data for forwarded X11 and TCP/IP connections).
432 The compression algorithm is the same used by
436 can be controlled by the
438 option for protocol version 1.
439 Compression is desirable on modem lines and other
440 slow connections, but will only slow down things on fast networks.
441 The default value can be set on a host-by-host basis in the
442 configuration files; see the
445 .It Fl c Ar blowfish | 3des | des
446 Selects the cipher to use for encrypting the session.
449 It is believed to be secure.
451 (triple-des) is an encrypt-decrypt-encrypt triple with three different keys.
453 is a fast block cipher; it appears very secure and is much faster than
456 is only supported in the
458 client for interoperability with legacy protocol 1 implementations
459 that do not support the
462 Its use is strongly discouraged due to cryptographic weaknesses.
463 .It Fl c Ar cipher_spec
464 Additionally, for protocol version 2 a comma-separated list of ciphers can
465 be specified in order of preference.
468 for more information.
472 application-level port forwarding.
473 This works by allocating a socket to listen to
475 on the local side, and whenever a connection is made to this port, the
476 connection is forwarded over the secure channel, and the application
477 protocol is then used to determine where to connect to from the
479 Currently the SOCKS4 and SOCKS5 protocols are supported, and
481 will act as a SOCKS server.
482 Only root can forward privileged ports.
483 Dynamic port forwardings can also be specified in the configuration file.
484 .It Fl e Ar ch | ^ch | none
485 Sets the escape character for sessions with a pty (default:
487 The escape character is only recognized at the beginning of a line.
488 The escape character followed by a dot
490 closes the connection;
491 followed by control-Z suspends the connection;
492 and followed by itself sends the escape character once.
493 Setting the character to
495 disables any escapes and makes the session fully transparent.
496 .It Fl F Ar configfile
497 Specifies an alternative per-user configuration file.
498 If a configuration file is given on the command line,
499 the system-wide configuration file
500 .Pq Pa /etc/ssh/ssh_config
502 The default for the per-user configuration file is
503 .Pa $HOME/.ssh/config .
507 to go to background just before command execution.
510 is going to ask for passwords or passphrases, but the user
511 wants it in the background.
514 The recommended way to start X11 programs at a remote site is with
516 .Ic ssh -f host xterm .
518 Allows remote hosts to connect to local forwarded ports.
519 .It Fl I Ar smartcard_device
520 Specifies which smartcard device to use.
521 The argument is the device
523 should use to communicate with a smartcard used for storing the user's
525 .It Fl i Ar identity_file
526 Selects a file from which the identity (private key) for
527 RSA or DSA authentication is read.
529 .Pa $HOME/.ssh/identity
530 for protocol version 1, and
531 .Pa $HOME/.ssh/id_rsa
533 .Pa $HOME/.ssh/id_dsa
534 for protocol version 2.
535 Identity files may also be specified on
536 a per-host basis in the configuration file.
537 It is possible to have multiple
539 options (and multiple identities specified in
540 configuration files).
542 Disables forwarding of Kerberos tickets.
543 This may also be specified on a per-host basis in the configuration file.
546 .Ar port : host : hostport
549 Specifies that the given port on the local (client) host is to be
550 forwarded to the given host and port on the remote side.
551 This works by allocating a socket to listen to
553 on the local side, and whenever a connection is made to this port, the
554 connection is forwarded over the secure channel, and a connection is
559 from the remote machine.
560 Port forwardings can also be specified in the configuration file.
561 Only root can forward privileged ports.
562 IPv6 addresses can be specified with an alternative syntax:
565 .Ar port No / Ar host No /
569 .It Fl l Ar login_name
570 Specifies the user to log in as on the remote machine.
571 This also may be specified on a per-host basis in the configuration file.
573 Additionally, for protocol version 2 a comma-separated list of MAC
574 (message authentication code) algorithms can
575 be specified in order of preference.
578 keyword for more information.
580 Do not execute a remote command.
581 This is useful for just forwarding ports
582 (protocol version 2 only).
586 (actually, prevents reading from stdin).
587 This must be used when
589 is run in the background.
590 A common trick is to use this to run X11 programs on a remote machine.
592 .Ic ssh -n shadows.cs.hut.fi emacs &
593 will start an emacs on shadows.cs.hut.fi, and the X11
594 connection will be automatically forwarded over an encrypted channel.
597 program will be put in the background.
598 (This does not work if
600 needs to ask for a password or passphrase; see also the
604 Can be used to give options in the format used in the configuration file.
605 This is useful for specifying options for which there is no separate
607 For full details of the options listed below, and their possible values, see
610 .Bl -tag -width Ds -offset indent -compact
614 .It ChallengeResponseAuthentication
618 .It ClearAllForwardings
621 .It ConnectionAttempts
622 .It ConnectionTimeout
627 .It ForwardX11Trusted
629 .It GlobalKnownHostsFile
630 .It GSSAPIAuthentication
631 .It GSSAPIDelegateCredentials
633 .It HostbasedAuthentication
634 .It HostKeyAlgorithms
642 .It NoHostAuthenticationForLocalhost
643 .It NumberOfPasswordPrompts
644 .It PasswordAuthentication
646 .It PreferredAuthentications
649 .It PubkeyAuthentication
651 .It RhostsRSAAuthentication
652 .It RSAAuthentication
654 .It StrictHostKeyChecking
655 .It UsePrivilegedPort
657 .It UserKnownHostsFile
662 Port to connect to on the remote host.
663 This can be specified on a
664 per-host basis in the configuration file.
667 Causes all warning and diagnostic messages to be suppressed.
670 .Ar port : host : hostport
673 Specifies that the given port on the remote (server) host is to be
674 forwarded to the given host and port on the local side.
675 This works by allocating a socket to listen to
677 on the remote side, and whenever a connection is made to this port, the
678 connection is forwarded over the secure channel, and a connection is
683 from the local machine.
684 Port forwardings can also be specified in the configuration file.
685 Privileged ports can be forwarded only when
686 logging in as root on the remote machine.
687 IPv6 addresses can be specified with an alternative syntax:
690 .Ar port No / Ar host No /
695 May be used to request invocation of a subsystem on the remote system.
696 Subsystems are a feature of the SSH2 protocol which facilitate the use
697 of SSH as a secure transport for other applications (eg.\&
699 The subsystem is specified as the remote command.
701 Disable pseudo-tty allocation.
703 Force pseudo-tty allocation.
704 This can be used to execute arbitrary
705 screen-based programs on a remote machine, which can be very useful,
706 e.g., when implementing menu services.
709 options force tty allocation, even if
713 Display the version number and exit.
718 to print debugging messages about its progress.
720 debugging connection, authentication, and configuration problems.
723 options increase the verbosity.
726 Enables X11 forwarding.
727 This can also be specified on a per-host basis in a configuration file.
729 X11 forwarding should be enabled with caution.
730 Users with the ability to bypass file permissions on the remote host
731 (for the user's X authorization database)
732 can access the local X11 display through the forwarded connection.
733 An attacker may then be able to perform activities such as keystroke monitoring.
735 Disables X11 forwarding.
737 Enables trusted X11 forwarding.
739 .Sh CONFIGURATION FILES
741 may additionally obtain configuration data from
742 a per-user configuration file and a system-wide configuration file.
743 The file format and configuration options are described in
747 will normally set the following environment variables:
748 .Bl -tag -width LOGNAME
752 variable indicates the location of the X11 server.
753 It is automatically set by
755 to point to a value of the form
757 where hostname indicates
758 the host where the shell runs, and n is an integer \*(Ge 1.
760 uses this special value to forward X11 connections over the secure
762 The user should normally not set
765 will render the X11 connection insecure (and will require the user to
766 manually copy any required authorization cookies).
768 Set to the path of the user's home directory.
772 set for compatibility with systems that use this variable.
774 Set to the path of the user's mailbox.
778 as specified when compiling
783 needs a passphrase, it will read the passphrase from the current
784 terminal if it was run from a terminal.
787 does not have a terminal associated with it but
791 are set, it will execute the program specified by
793 and open an X11 window to read the passphrase.
794 This is particularly useful when calling
799 (Note that on some machines it
800 may be necessary to redirect the input from
804 Identifies the path of a unix-domain socket used to communicate with the
806 .It Ev SSH_CONNECTION
807 Identifies the client and server ends of the connection.
808 The variable contains
809 four space-separated values: client ip-address, client port number,
810 server ip-address and server port number.
811 .It Ev SSH_ORIGINAL_COMMAND
812 The variable contains the original command line if a forced command
814 It can be used to extract the original arguments.
816 This is set to the name of the tty (path to the device) associated
817 with the current shell or command.
818 If the current session has no tty,
819 this variable is not set.
821 The timezone variable is set to indicate the present timezone if it
822 was set when the daemon was started (i.e., the daemon passes the value
823 on to new connections).
825 Set to the name of the user logging in.
831 .Pa $HOME/.ssh/environment ,
832 and adds lines of the format
834 to the environment if the file exists and if users are allowed to
835 change their environment.
836 For more information, see the
837 .Cm PermitUserEnvironment
842 .It Pa $HOME/.ssh/known_hosts
843 Records host keys for all hosts the user has logged into that are not
845 .Pa /etc/ssh/ssh_known_hosts .
848 .It Pa $HOME/.ssh/identity, $HOME/.ssh/id_dsa, $HOME/.ssh/id_rsa
849 Contains the authentication identity of the user.
850 They are for protocol 1 RSA, protocol 2 DSA, and protocol 2 RSA, respectively.
852 contain sensitive data and should be readable by the user but not
853 accessible by others (read/write/execute).
856 ignores a private key file if it is accessible by others.
857 It is possible to specify a passphrase when
858 generating the key; the passphrase will be used to encrypt the
859 sensitive part of this file using 3DES.
860 .It Pa $HOME/.ssh/identity.pub, $HOME/.ssh/id_dsa.pub, $HOME/.ssh/id_rsa.pub
861 Contains the public key for authentication (public part of the
862 identity file in human-readable form).
864 .Pa $HOME/.ssh/identity.pub
865 file should be added to the file
866 .Pa $HOME/.ssh/authorized_keys
868 where the user wishes to log in using protocol version 1 RSA authentication.
870 .Pa $HOME/.ssh/id_dsa.pub
872 .Pa $HOME/.ssh/id_rsa.pub
873 file should be added to
874 .Pa $HOME/.ssh/authorized_keys
876 where the user wishes to log in using protocol version 2 DSA/RSA authentication.
878 sensitive and can (but need not) be readable by anyone.
880 never used automatically and are not necessary; they are only provided for
881 the convenience of the user.
882 .It Pa $HOME/.ssh/config
883 This is the per-user configuration file.
884 The file format and configuration options are described in
886 .It Pa $HOME/.ssh/authorized_keys
887 Lists the public keys (RSA/DSA) that can be used for logging in as this user.
888 The format of this file is described in the
891 In the simplest form the format is the same as the
894 This file is not highly sensitive, but the recommended
895 permissions are read/write for the user, and not accessible by others.
896 .It Pa /etc/ssh/ssh_known_hosts
897 Systemwide list of known host keys.
898 This file should be prepared by the
899 system administrator to contain the public host keys of all machines in the
901 This file should be world-readable.
903 public keys, one per line, in the following format (fields separated
904 by spaces): system name, public key and optional comment field.
905 When different names are used
906 for the same machine, all such names should be listed, separated by
908 The format is described in the
912 The canonical system name (as returned by name servers) is used by
914 to verify the client host when logging in; other names are needed because
916 does not convert the user-supplied name to a canonical name before
917 checking the key, because someone with access to the name servers
918 would then be able to fool host authentication.
919 .It Pa /etc/ssh/ssh_config
920 Systemwide configuration file.
921 The file format and configuration options are described in
923 .It Pa /etc/ssh/ssh_host_key, /etc/ssh/ssh_host_dsa_key, /etc/ssh/ssh_host_rsa_key
924 These three files contain the private parts of the host keys
926 .Cm RhostsRSAAuthentication
928 .Cm HostbasedAuthentication .
929 If the protocol version 1
930 .Cm RhostsRSAAuthentication
933 must be setuid root, since the host key is readable only by root.
934 For protocol version 2,
938 to access the host keys for
939 .Cm HostbasedAuthentication .
940 This eliminates the requirement that
942 be setuid root when that authentication method is used.
949 authentication to list the
950 host/user pairs that are permitted to log in.
951 (Note that this file is
952 also used by rlogin and rsh, which makes using this file insecure.)
953 Each line of the file contains a host name (in the canonical form
954 returned by name servers), and then a user name on that host,
955 separated by a space.
956 On some machines this file may need to be
957 world-readable if the user's home directory is on a NFS partition,
961 Additionally, this file must be owned by the user,
962 and must not have write permissions for anyone else.
964 permission for most machines is read/write for the user, and not
965 accessible by others.
969 will be installed so that it requires successful RSA host
970 authentication before permitting
973 If the server machine does not have the client's host key in
974 .Pa /etc/ssh/ssh_known_hosts ,
976 .Pa $HOME/.ssh/known_hosts .
977 The easiest way to do this is to
978 connect back to the client from the server machine using ssh; this
979 will automatically add the host key to
980 .Pa $HOME/.ssh/known_hosts .
982 This file is used exactly the same way as
985 having this file is to be able to use rhosts authentication with
987 without permitting login with
991 .It Pa /etc/hosts.equiv
992 This file is used during
996 canonical hosts names, one per line (the full format is described in the
999 If the client host is found in this file, login is
1000 automatically permitted provided client and server user names are the
1002 Additionally, successful RSA host authentication is normally
1004 This file should only be writable by root.
1005 .It Pa /etc/shosts.equiv
1006 This file is processed exactly as
1007 .Pa /etc/hosts.equiv .
1008 This file may be useful to permit logins using
1010 but not using rsh/rlogin.
1011 .It Pa /etc/ssh/sshrc
1012 Commands in this file are executed by
1014 when the user logs in just before the user's shell (or command) is started.
1017 manual page for more information.
1018 .It Pa $HOME/.ssh/rc
1019 Commands in this file are executed by
1021 when the user logs in just before the user's shell (or command) is
1025 manual page for more information.
1026 .It Pa $HOME/.ssh/environment
1027 Contains additional definitions for environment variables, see section
1033 exits with the exit status of the remote command or with 255
1034 if an error occurred.
1054 .%T "SSH Protocol Architecture"
1055 .%N draft-ietf-secsh-architecture-12.txt
1057 .%O work in progress material
1060 OpenSSH is a derivative of the original and free
1061 ssh 1.2.12 release by Tatu Ylonen.
1062 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
1063 Theo de Raadt and Dug Song
1064 removed many bugs, re-added newer features and
1066 Markus Friedl contributed the support for SSH
1067 protocol versions 1.5 and 2.0.
andersk / openssh.git / blob