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 .Dd September 25, 1999
42 .Nd secure shell daemon
47 .Op Fl f Ar config_file
48 .Op Fl g Ar login_grace_time
49 .Op Fl h Ar host_key_file
50 .Op Fl k Ar key_gen_time
53 .Op Fl V Ar client_protocol_id
56 (Secure Shell Daemon) is the daemon program for
58 Together these programs replace rlogin and rsh, and
59 provide secure encrypted communications between two untrusted hosts
60 over an insecure network.
61 The programs are intended to be as easy to
62 install and use as possible.
65 is the daemon that listens for connections from clients.
66 It is normally started at boot from
69 daemon for each incoming connection.
70 The forked daemons handle
71 key exchange, encryption, authentication, command execution,
73 This implementation of
75 supports both SSH protocol version 1 and 2 simultaneously.
79 .Ss SSH protocol version 1
81 Each host has a host-specific RSA key
82 (normally 1024 bits) used to identify the host.
84 the daemon starts, it generates a server RSA key (normally 768 bits).
85 This key is normally regenerated every hour if it has been used, and
86 is never stored on disk.
88 Whenever a client connects the daemon responds with its public
90 The client compares the
91 RSA host key against its own database to verify that it has not changed.
92 The client then generates a 256 bit random number.
94 random number using both the host key and the server key, and sends
95 the encrypted number to the server.
96 Both sides then use this
97 random number as a session key which is used to encrypt all further
98 communications in the session.
99 The rest of the session is encrypted
100 using a conventional cipher, currently Blowfish or 3DES, with 3DES
101 being used by default.
102 The client selects the encryption algorithm
103 to use from those offered by the server.
105 Next, the server and the client enter an authentication dialog.
106 The client tries to authenticate itself using
110 authentication combined with RSA host
111 authentication, RSA challenge-response authentication, or password
112 based authentication.
114 Rhosts authentication is normally disabled
115 because it is fundamentally insecure, but can be enabled in the server
116 configuration file if desired.
117 System security is not improved unless
123 are disabled (thus completely disabling
129 .Ss SSH protocol version 2
131 Version 2 works similarly:
132 Each host has a host-specific DSA key used to identify the host.
133 However, when the daemon starts, it does not generate a server key.
134 Forward security is provided through a Diffie-Hellman key agreement.
135 This key agreement results in a shared session key.
136 The rest of the session is encrypted
137 using a symmetric cipher, currently
138 Blowfish, 3DES or CAST128 in CBC mode or Arcfour.
139 The client selects the encryption algorithm
140 to use from those offered by the server.
141 Additionally, session integrity is provided
142 through a cryptographic message authentication code
143 (hmac-sha1 or hmac-md5).
145 Protocol version 2 provides a public key based
146 user authentication method (DSAAuthentication)
147 and conventional password authentication.
149 .Ss Command execution and data forwarding
151 If the client successfully authenticates itself, a dialog for
152 preparing the session is entered.
153 At this time the client may request
154 things like allocating a pseudo-tty, forwarding X11 connections,
155 forwarding TCP/IP connections, or forwarding the authentication agent
156 connection over the secure channel.
158 Finally, the client either requests a shell or execution of a command.
159 The sides then enter session mode.
160 In this mode, either side may send
161 data at any time, and such data is forwarded to/from the shell or
162 command on the server side, and the user terminal in the client side.
164 When the user program terminates and all forwarded X11 and other
165 connections have been closed, the server sends command exit status to
166 the client, and both sides exit.
169 can be configured using command-line options or a configuration
171 Command-line options override values specified in the
175 rereads its configuration file when it receives a hangup signal,
178 The options are as follows:
181 Specifies the number of bits in the server key (default 768).
185 The server sends verbose debug output to the system
186 log, and does not put itself in the background.
187 The server also will not fork and will only process one connection.
188 This option is only intended for debugging for the server.
189 Multiple -d options increases the debugging level.
191 .It Fl f Ar configuration_file
192 Specifies the name of the configuration file.
194 .Pa /etc/sshd_config .
196 refuses to start if there is no configuration file.
197 .It Fl g Ar login_grace_time
198 Gives the grace time for clients to authenticate themselves (default
200 If the client fails to authenticate the user within
201 this many seconds, the server disconnects and exits.
202 A value of zero indicates no limit.
203 .It Fl h Ar host_key_file
204 Specifies the file from which the RSA host key is read (default
205 .Pa /etc/ssh_host_key ) .
206 This option must be given if
208 is not run as root (as the normal
209 host file is normally not readable by anyone but root).
213 is being run from inetd.
216 from inetd because it needs to generate the server key before it can
217 respond to the client, and this may take tens of seconds.
218 Clients would have to wait too long if the key was regenerated every time.
219 However, with small key sizes (e.g., 512) using
223 .It Fl k Ar key_gen_time
224 Specifies how often the server key is regenerated (default 3600
225 seconds, or one hour).
226 The motivation for regenerating the key fairly
227 often is that the key is not stored anywhere, and after about an hour,
228 it becomes impossible to recover the key for decrypting intercepted
229 communications even if the machine is cracked into or physically
231 A value of zero indicates that the key will never be regenerated.
233 Specifies the port on which the server listens for connections
237 Nothing is sent to the system log.
238 Normally the beginning,
239 authentication, and termination of each connection is logged.
241 This option is used to specify the size of the field
244 structure that holds the remote host name.
245 If the resolved host name is longer than
247 the dotted decimal value will be used instead.
248 This allows hosts with very long host names that
249 overflow this field to still be uniquely identified.
252 indicates that only dotted decimal addresses
253 should be put into the
257 Do not print an error message if RSA support is missing.
258 .It Fl V Ar client_protocol_id
259 SSH-2 compatibility mode.
260 When this option is specified
262 assumes the client has sent the supplied version string
264 Protocol Version Identification Exchange.
265 This option is not intended to be called directly.
269 to use IPv4 addresses only.
273 to use IPv6 addresses only.
275 .Sh CONFIGURATION FILE
277 reads configuration data from
279 (or the file specified with
281 on the command line).
282 The file contains keyword-value pairs, one per line.
285 and empty lines are interpreted as comments.
287 The following keywords are possible.
289 .It Cm AFSTokenPassing
290 Specifies whether an AFS token may be forwarded to the server.
294 This keyword can be followed by a number of group names, separated
296 If specified, login is allowed only for users whose primary
297 group matches one of the patterns.
302 wildcards in the patterns.
303 Only group names are valid; a numerical group ID isn't recognized.
304 By default login is allowed regardless of the primary group.
306 .It Cm AllowTcpForwarding
307 Specifies whether TCP forwarding is permitted.
310 Note that disabling TCP forwarding does not improve security unless
311 users are also denied shell access, as they can always install their
315 This keyword can be followed by a number of user names, separated
317 If specified, login is allowed only for users names that
318 match one of the patterns.
323 wildcards in the patterns.
324 Only user names are valid; a numerical user ID isn't recognized.
325 By default login is allowed regardless of the user name.
328 Specifies the ciphers allowed for protocol version 2.
329 Multiple ciphers must be comma-separated.
331 .Dq 3des-cbc,blowfish-cbc,arcfour,cast128-cbc .
335 should check for new mail for interactive logins.
339 This keyword can be followed by a number of group names, separated
341 Users whose primary group matches one of the patterns
342 aren't allowed to log in.
347 wildcards in the patterns.
348 Only group names are valid; a numerical group ID isn't recognized.
349 By default login is allowed regardless of the primary group.
352 This keyword can be followed by a number of user names, separated
354 Login is disallowed for user names that match one of the patterns.
358 can be used as wildcards in the patterns.
359 Only user names are valid; a numerical user ID isn't recognized.
360 By default login is allowed regardless of the user name.
361 .It Cm DSAAuthentication
362 Specifies whether DSA authentication is allowed.
365 Note that this option applies to protocol version 2 only.
367 Specifies whether remote hosts are allowed to connect to ports
368 forwarded for the client.
376 Specifies the file containing the private DSA host key (default
377 .Pa /etc/ssh_host_dsa_key )
378 used by SSH protocol 2.0.
381 disables protocol 2.0 if this file is group/world-accessible.
383 Specifies the file containing the private RSA host key (default
384 .Pa /etc/ssh_host_key )
385 used by SSH protocols 1.3 and 1.5.
388 disables protocols 1.3 and 1.5 if this file is group/world-accessible.
394 files will not be used in authentication.
397 .Pa /etc/shosts.equiv
401 .It Cm IgnoreUserKnownHosts
404 should ignore the user's
405 .Pa $HOME/.ssh/known_hosts
407 .Cm RhostsRSAAuthentication .
411 Specifies whether the system should send keepalive messages to the
413 If they are sent, death of the connection or crash of one
414 of the machines will be properly noticed.
415 However, this means that
416 connections will die if the route is down temporarily, and some people
418 On the other hand, if keepalives are not sent,
419 sessions may hang indefinitely on the server, leaving
421 users and consuming server resources.
425 (to send keepalives), and the server will notice
426 if the network goes down or the client host reboots.
427 This avoids infinitely hanging sessions.
429 To disable keepalives, the value should be set to
431 in both the server and the client configuration files.
432 .It Cm KerberosAuthentication
433 Specifies whether Kerberos authentication is allowed.
434 This can be in the form of a Kerberos ticket, or if
435 .Cm PasswordAuthentication
436 is yes, the password provided by the user will be validated through
438 To use this option, the server needs a
439 Kerberos servtab which allows the verification of the KDC's identity.
442 .It Cm KerberosOrLocalPasswd
443 If set then if password authentication through Kerberos fails then
444 the password will be validated via any additional local mechanism
449 .It Cm KerberosTgtPassing
450 Specifies whether a Kerberos TGT may be forwarded to the server.
453 as this only works when the Kerberos KDC is actually an AFS kaserver.
454 .It Cm KerberosTicketCleanup
455 Specifies whether to automatically destroy the user's ticket cache
459 .It Cm KeyRegenerationInterval
460 The server key is automatically regenerated after this many seconds
461 (if it has been used).
462 The purpose of regeneration is to prevent
463 decrypting captured sessions by later breaking into the machine and
465 The key is never stored anywhere.
466 If the value is 0, the key is never regenerated.
467 The default is 3600 (seconds).
469 Specifies what local address
472 The default is to listen to all local addresses.
473 Multiple options of this type are permitted.
476 options must precede this option.
477 .It Cm LoginGraceTime
478 The server disconnects after this time if the user has not
479 successfully logged in.
480 If the value is 0, there is no time limit.
481 The default is 600 (seconds).
483 Gives the verbosity level that is used when logging messages from
485 The possible values are:
486 QUIET, FATAL, ERROR, INFO, VERBOSE and DEBUG.
488 Logging with level DEBUG violates the privacy of users
489 and is not recommended.
491 Specifies the maximum number of concurrent unauthenticated connections to the
494 Additional connections will be dropped until authentication succeeds or the
496 expires for a connection.
499 Alternatively, random early drop can be enabled by specifying
500 the three colon separated values
504 will refuse connection attempts with a probabillity of
507 if there are currently
510 unauthenticated connections.
511 The probabillity increases linearly and all connection attempts
512 are refused if the number of unauthenticated connections reaches
515 .It Cm PasswordAuthentication
516 Specifies whether password authentication is allowed.
519 Note that this option applies to both protocol versions 1 and 2.
520 .It Cm PermitEmptyPasswords
521 When password authentication is allowed, it specifies whether the
522 server allows login to accounts with empty password strings.
525 .It Cm PermitRootLogin
526 Specifies whether the root can log in using
535 If this options is set to
537 only password authentication is disabled for root.
539 Root login with RSA authentication when the
542 specified will be allowed regardless of the value of this setting
543 (which may be useful for taking remote backups even if root login is
544 normally not allowed).
546 Specifies the file that contains the process identifier of the
550 .Pa /var/run/sshd.pid .
552 Specifies the port number that
556 Multiple options of this type are permitted.
562 when a user logs in interactively.
563 (On some systems it is also printed by the shell,
569 Specifies the protocol versions
572 The possible values are
576 Multiple versions must be comma-separated.
581 Random number generation uses other techniques.
582 .It Cm RhostsAuthentication
583 Specifies whether authentication using rhosts or /etc/hosts.equiv
585 Normally, this method should not be permitted because it is insecure.
586 .Cm RhostsRSAAuthentication
588 instead, because it performs RSA-based host authentication in addition
589 to normal rhosts or /etc/hosts.equiv authentication.
592 .It Cm RhostsRSAAuthentication
593 Specifies whether rhosts or /etc/hosts.equiv authentication together
594 with successful RSA host authentication is allowed.
597 .It Cm RSAAuthentication
598 Specifies whether pure RSA authentication is allowed.
601 Note that this option applies to protocol version 1 only.
603 Defines the number of bits in the server key.
604 The minimum value is 512, and the default is 768.
605 .It Cm SkeyAuthentication
608 authentication is allowed.
611 Note that s/key authentication is enabled only if
612 .Cm PasswordAuthentication
617 should check file modes and ownership of the
618 user's files and home directory before accepting login.
619 This is normally desirable because novices sometimes accidentally leave their
620 directory or files world-writable.
624 Configures an external subsystem (e.g., file transfer daemon).
625 Arguments should be a subsystem name and a command to execute upon subsystem
631 file transfer subsystem.
632 By default no subsystems are defined.
633 Note that this option applies to protocol version 2 only.
634 .It Cm SyslogFacility
635 Gives the facility code that is used when logging messages from
637 The possible values are: DAEMON, USER, AUTH, LOCAL0, LOCAL1, LOCAL2,
638 LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.
643 is used for interactive login sessions.
646 is never used for remote command execution.
649 .It Cm X11DisplayOffset
650 Specifies the first display number available for
655 from interfering with real X11 servers.
658 Specifies whether X11 forwarding is permitted.
661 Note that disabling X11 forwarding does not improve security in any
662 way, as users can always install their own forwarders.
664 Specifies the location of the
668 .Pa /usr/X11R6/bin/xauth .
671 When a user successfully logs in,
674 .Bl -enum -offset indent
676 If the login is on a tty, and no command has been specified,
677 prints last login time and
679 (unless prevented in the configuration file or by
680 .Pa $HOME/.hushlogin ;
685 If the login is on a tty, records login time.
689 if it exists, prints contents and quits
692 Changes to run with normal user privileges.
694 Sets up basic environment.
697 .Pa $HOME/.ssh/environment
700 Changes to user's home directory.
704 exists, runs it; else if
707 it; otherwise runs xauth.
710 files are given the X11
711 authentication protocol and cookie in standard input.
713 Runs user's shell or command.
715 .Sh AUTHORIZED_KEYS FILE FORMAT
717 .Pa $HOME/.ssh/authorized_keys
718 file lists the RSA keys that are
719 permitted for RSA authentication in SSH protocols 1.3 and 1.5
721 .Pa $HOME/.ssh/authorized_keys2
722 file lists the DSA keys that are
723 permitted for DSA authentication in SSH protocol 2.0.
724 Each line of the file contains one
725 key (empty lines and lines starting with a
729 Each line consists of the following fields, separated by
730 spaces: options, bits, exponent, modulus, comment.
732 is optional; its presence is determined by whether the line starts
733 with a number or not (the option field never starts with a number).
734 The bits, exponent, modulus and comment fields give the RSA key; the
735 comment field is not used for anything (but may be convenient for the
736 user to identify the key).
738 Note that lines in this file are usually several hundred bytes long
739 (because of the size of the RSA key modulus).
740 You don't want to type them in; instead, copy the
744 The options (if present) consist of comma-separated option
746 No spaces are permitted, except within double quotes.
747 The following option specifications are supported:
749 .It Cm from="pattern-list"
750 Specifies that in addition to RSA authentication, the canonical name
751 of the remote host must be present in the comma-separated list of
757 The list may also contain
758 patterns negated by prefixing them with
760 if the canonical host name matches a negated pattern, the key is not accepted.
762 of this option is to optionally increase security: RSA authentication
763 by itself does not trust the network or name servers or anything (but
764 the key); however, if somebody somehow steals the key, the key
765 permits an intruder to log in from anywhere in the world.
766 This additional option makes using a stolen key more difficult (name
767 servers and/or routers would have to be compromised in addition to
769 .It Cm command="command"
770 Specifies that the command is executed whenever this key is used for
772 The command supplied by the user (if any) is ignored.
773 The command is run on a pty if the connection requests a pty;
774 otherwise it is run without a tty.
775 A quote may be included in the command by quoting it with a backslash.
776 This option might be useful
777 to restrict certain RSA keys to perform just a specific operation.
778 An example might be a key that permits remote backups but nothing else.
779 Note that the client may specify TCP/IP and/or X11
780 forwarding unless they are explicitly prohibited.
781 .It Cm environment="NAME=value"
782 Specifies that the string is to be added to the environment when
783 logging in using this key.
784 Environment variables set this way
785 override other default environment values.
786 Multiple options of this type are permitted.
787 .It Cm no-port-forwarding
788 Forbids TCP/IP forwarding when this key is used for authentication.
789 Any port forward requests by the client will return an error.
790 This might be used, e.g., in connection with the
793 .It Cm no-X11-forwarding
794 Forbids X11 forwarding when this key is used for authentication.
795 Any X11 forward requests by the client will return an error.
796 .It Cm no-agent-forwarding
797 Forbids authentication agent forwarding when this key is used for
800 Prevents tty allocation (a request to allocate a pty will fail).
803 1024 33 12121.\|.\|.\|312314325 ylo@foo.bar
805 from="*.niksula.hut.fi,!pc.niksula.hut.fi" 1024 35 23.\|.\|.\|2334 ylo@niksula
807 command="dump /home",no-pty,no-port-forwarding 1024 33 23.\|.\|.\|2323 backup.hut.fi
808 .Sh SSH_KNOWN_HOSTS FILE FORMAT
810 .Pa /etc/ssh_known_hosts ,
811 .Pa /etc/ssh_known_hosts2 ,
812 .Pa $HOME/.ssh/known_hosts ,
814 .Pa $HOME/.ssh/known_hosts2
815 files contain host public keys for all known hosts.
816 The global file should
817 be prepared by the administrator (optional), and the per-user file is
818 maintained automatically: whenever the user connects from an unknown host
819 its key is added to the per-user file.
821 Each line in these files contains the following fields: hostnames,
822 bits, exponent, modulus, comment.
823 The fields are separated by spaces.
825 Hostnames is a comma-separated list of patterns ('*' and '?' act as
826 wildcards); each pattern in turn is matched against the canonical host
827 name (when authenticating a client) or against the user-supplied
828 name (when authenticating a server).
829 A pattern may also be preceded by
831 to indicate negation: if the host name matches a negated
832 pattern, it is not accepted (by that line) even if it matched another
835 Bits, exponent, and modulus are taken directly from the RSA host key; they
836 can be obtained, e.g., from
837 .Pa /etc/ssh_host_key.pub .
838 The optional comment field continues to the end of the line, and is not used.
842 and empty lines are ignored as comments.
844 When performing host authentication, authentication is accepted if any
845 matching line has the proper key.
846 It is thus permissible (but not
847 recommended) to have several lines or different host keys for the same
849 This will inevitably happen when short forms of host names
850 from different domains are put in the file.
852 that the files contain conflicting information; authentication is
853 accepted if valid information can be found from either file.
855 Note that the lines in these files are typically hundreds of characters
856 long, and you definitely don't want to type in the host keys by hand.
857 Rather, generate them by a script
859 .Pa /etc/ssh_host_key.pub
860 and adding the host names at the front.
862 closenet,closenet.hut.fi,.\|.\|.\|,130.233.208.41 1024 37 159.\|.\|.93 closenet.hut.fi
865 .It Pa /etc/sshd_config
866 Contains configuration data for
868 This file should be writable by root only, but it is recommended
869 (though not necessary) that it be world-readable.
870 .It Pa /etc/ssh_host_key
871 Contains the private part of the host key.
872 This file should only be owned by root, readable only by root, and not
873 accessible to others.
876 does not start if this file is group/world-accessible.
877 .It Pa /etc/ssh_host_key.pub
878 Contains the public part of the host key.
879 This file should be world-readable but writable only by
881 Its contents should match the private part.
883 really used for anything; it is only provided for the convenience of
884 the user so its contents can be copied to known hosts files.
885 These two files are created using
887 .It Pa /var/run/sshd.pid
888 Contains the process ID of the
890 listening for connections (if there are several daemons running
891 concurrently for different ports, this contains the pid of the one
893 The content of this file is not sensitive; it can be world-readable.
894 .It Pa $HOME/.ssh/authorized_keys
895 Lists the RSA keys that can be used to log into the user's account.
896 This file must be readable by root (which may on some machines imply
897 it being world-readable if the user's home directory resides on an NFS
899 It is recommended that it not be accessible by others.
900 The format of this file is described above.
901 Users will place the contents of their
903 files into this file, as described in
905 .It Pa $HOME/.ssh/authorized_keys2
906 Lists the DSA keys that can be used to log into the user's account.
907 This file must be readable by root (which may on some machines imply
908 it being world-readable if the user's home directory resides on an NFS
910 It is recommended that it not be accessible by others.
911 The format of this file is described above.
912 Users will place the contents of their
914 files into this file, as described in
916 .It Pa "/etc/ssh_known_hosts" and "$HOME/.ssh/known_hosts"
917 These files are consulted when using rhosts with RSA host
918 authentication to check the public key of the host.
919 The key must be listed in one of these files to be accepted.
920 The client uses the same files
921 to verify that the remote host is the one it intended to connect.
922 These files should be writable only by root/the owner.
923 .Pa /etc/ssh_known_hosts
924 should be world-readable, and
925 .Pa $HOME/.ssh/known_hosts
926 can but need not be world-readable.
930 refuses to let anyone except root log in.
931 The contents of the file
932 are displayed to anyone trying to log in, and non-root connections are
934 The file should be world-readable.
935 .It Pa /etc/hosts.allow, /etc/hosts.deny
938 support, tcp-wrappers access controls may be defined here as described in
941 This file contains host-username pairs, separated by a space, one per
943 The given user on the corresponding host is permitted to log in
945 The same file is used by rlogind and rshd.
947 be writable only by the user; it is recommended that it not be
948 accessible by others.
950 If is also possible to use netgroups in the file.
952 name may be of the form +@groupname to specify all hosts or all users
956 this file is exactly the same as for
958 However, this file is
959 not used by rlogin and rshd, so using this permits access using SSH only.
960 .It Pa /etc/hosts.equiv
961 This file is used during
964 In the simplest form, this file contains host names, one per line.
966 those hosts are permitted to log in without a password, provided they
967 have the same user name on both machines.
968 The host name may also be
969 followed by a user name; such users are permitted to log in as
971 user on this machine (except root).
972 Additionally, the syntax
974 can be used to specify netgroups.
975 Negated entries start with
978 If the client host/user is successfully matched in this file, login is
979 automatically permitted provided the client and server user names are the
981 Additionally, successful RSA host authentication is normally required.
982 This file must be writable only by root; it is recommended
983 that it be world-readable.
985 .Sy "Warning: It is almost never a good idea to use user names in"
987 Beware that it really means that the named user(s) can log in as
989 which includes bin, daemon, adm, and other accounts that own critical
990 binaries and directories.
991 Using a user name practically grants the user root access.
992 The only valid use for user names that I can think
993 of is in negative entries.
995 Note that this warning also applies to rsh/rlogin.
996 .It Pa /etc/shosts.equiv
997 This is processed exactly as
998 .Pa /etc/hosts.equiv .
999 However, this file may be useful in environments that want to run both
1001 .It Pa $HOME/.ssh/environment
1002 This file is read into the environment at login (if it exists).
1003 It can only contain empty lines, comment lines (that start with
1005 and assignment lines of the form name=value.
1006 The file should be writable
1007 only by the user; it need not be readable by anyone else.
1008 .It Pa $HOME/.ssh/rc
1009 If this file exists, it is run with /bin/sh after reading the
1010 environment files but before starting the user's shell or command.
1011 If X11 spoofing is in use, this will receive the "proto cookie" pair in
1019 The primary purpose of this file is to run any initialization routines
1020 which may be needed before the user's home directory becomes
1021 accessible; AFS is a particular example of such an environment.
1023 This file will probably contain some initialization code followed by
1024 something similar to: "if read proto cookie; then echo add $DISPLAY
1025 $proto $cookie | xauth -q -; fi".
1027 If this file does not exist,
1030 does not exist either, xauth is used to store the cookie.
1032 This file should be writable only by the user, and need not be
1033 readable by anyone else.
1037 This can be used to specify
1038 machine-specific login-time initializations globally.
1039 This file should be writable only by root, and should be world-readable.
1043 is a derivative of the original (free) ssh 1.2.12 release by Tatu Ylonen,
1044 but with bugs removed and newer features re-added.
1046 1.2.12 release, newer versions of the original ssh bore successively
1047 more restrictive licenses, and thus demand for a free version was born.
1049 This version of OpenSSH
1052 has all components of a restrictive nature (i.e., patents, see
1054 directly removed from the source code; any licensed or patented components
1058 has been updated to support SSH protocol 1.5 and 2, making it compatible with
1059 all other SSH clients and servers.
1061 contains added support for
1063 authentication and ticket passing.
1065 supports one-time password authentication with
1069 OpenSSH has been created by Aaron Campbell, Bob Beck, Markus Friedl,
1070 Niels Provos, Theo de Raadt, and Dug Song.
1072 The support for SSH protocol 2 was written by Markus Friedl.