1.\" 2.\" Author: Tatu Ylonen <ylo@cs.hut.fi> 3.\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland 4.\" All rights reserved 5.\" 6.\" As far as I am concerned, the code I have written for this software 7.\" can be used freely for any purpose. Any derived versions of this 8.\" software must be clearly marked as such, and if the derived work is 9.\" incompatible with the protocol description in the RFC file, it must be 10.\" called by a name other than "ssh" or "Secure Shell". 11.\" 12.\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved. 13.\" Copyright (c) 1999 Aaron Campbell. All rights reserved. 14.\" Copyright (c) 1999 Theo de Raadt. All rights reserved. 15.\" 16.\" Redistribution and use in source and binary forms, with or without 17.\" modification, are permitted provided that the following conditions 18.\" are met: 19.\" 1. Redistributions of source code must retain the above copyright 20.\" notice, this list of conditions and the following disclaimer. 21.\" 2. Redistributions in binary form must reproduce the above copyright 22.\" notice, this list of conditions and the following disclaimer in the 23.\" documentation and/or other materials provided with the distribution. 24.\" 25.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 26.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 27.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 28.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 29.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 30.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 31.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 32.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 33.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 34.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 35.\" 36.\" $OpenBSD: sshd.8,v 1.263 2011/08/02 01:22:11 djm Exp $ 37.Dd $Mdocdate: August 2 2011 $ 38.Dt SSHD 8 39.Os 40.Sh NAME 41.Nm sshd 42.Nd OpenSSH SSH daemon 43.Sh SYNOPSIS 44.Nm sshd 45.Bk -words 46.Op Fl 46DdeiqTt 47.Op Fl b Ar bits 48.Op Fl C Ar connection_spec 49.Op Fl c Ar host_certificate_file 50.Op Fl f Ar config_file 51.Op Fl g Ar login_grace_time 52.Op Fl h Ar host_key_file 53.Op Fl k Ar key_gen_time 54.Op Fl o Ar option 55.Op Fl p Ar port 56.Op Fl u Ar len 57.Ek 58.Sh DESCRIPTION 59.Nm 60(OpenSSH Daemon) is the daemon program for 61.Xr ssh 1 . 62Together these programs replace 63.Xr rlogin 1 64and 65.Xr rsh 1 , 66and provide secure encrypted communications between two untrusted hosts 67over an insecure network. 68.Pp 69.Nm 70listens for connections from clients. 71It is normally started at boot from 72.Pa /etc/rc . 73It forks a new 74daemon for each incoming connection. 75The forked daemons handle 76key exchange, encryption, authentication, command execution, 77and data exchange. 78.Pp 79.Nm 80can be configured using command-line options or a configuration file 81(by default 82.Xr sshd_config 5 ) ; 83command-line options override values specified in the 84configuration file. 85.Nm 86rereads its configuration file when it receives a hangup signal, 87.Dv SIGHUP , 88by executing itself with the name and options it was started with, e.g.\& 89.Pa /usr/sbin/sshd . 90.Pp 91The options are as follows: 92.Bl -tag -width Ds 93.It Fl 4 94Forces 95.Nm 96to use IPv4 addresses only. 97.It Fl 6 98Forces 99.Nm 100to use IPv6 addresses only. 101.It Fl b Ar bits 102Specifies the number of bits in the ephemeral protocol version 1 103server key (default 1024). 104.It Fl C Ar connection_spec 105Specify the connection parameters to use for the 106.Fl T 107extended test mode. 108If provided, any 109.Cm Match 110directives in the configuration file 111that would apply to the specified user, host, and address will be set before 112the configuration is written to standard output. 113The connection parameters are supplied as keyword=value pairs. 114The keywords are 115.Dq user , 116.Dq host , 117and 118.Dq addr . 119All are required and may be supplied in any order, either with multiple 120.Fl C 121options or as a comma-separated list. 122.It Fl c Ar host_certificate_file 123Specifies a path to a certificate file to identify 124.Nm 125during key exchange. 126The certificate file must match a host key file specified using the 127.Fl h 128option or the 129.Cm HostKey 130configuration directive. 131.It Fl D 132When this option is specified, 133.Nm 134will not detach and does not become a daemon. 135This allows easy monitoring of 136.Nm sshd . 137.It Fl d 138Debug mode. 139The server sends verbose debug output to standard error, 140and does not put itself in the background. 141The server also will not fork and will only process one connection. 142This option is only intended for debugging for the server. 143Multiple 144.Fl d 145options increase the debugging level. 146Maximum is 3. 147.It Fl e 148When this option is specified, 149.Nm 150will send the output to the standard error instead of the system log. 151.It Fl f Ar config_file 152Specifies the name of the configuration file. 153The default is 154.Pa /etc/ssh/sshd_config . 155.Nm 156refuses to start if there is no configuration file. 157.It Fl g Ar login_grace_time 158Gives the grace time for clients to authenticate themselves (default 159120 seconds). 160If the client fails to authenticate the user within 161this many seconds, the server disconnects and exits. 162A value of zero indicates no limit. 163.It Fl h Ar host_key_file 164Specifies a file from which a host key is read. 165This option must be given if 166.Nm 167is not run as root (as the normal 168host key files are normally not readable by anyone but root). 169The default is 170.Pa /etc/ssh/ssh_host_key 171for protocol version 1, and 172.Pa /etc/ssh/ssh_host_dsa_key , 173.Pa /etc/ssh/ssh_host_ecdsa_key 174and 175.Pa /etc/ssh/ssh_host_rsa_key 176for protocol version 2. 177It is possible to have multiple host key files for 178the different protocol versions and host key algorithms. 179.It Fl i 180Specifies that 181.Nm 182is being run from 183.Xr inetd 8 . 184.Nm 185is normally not run 186from inetd because it needs to generate the server key before it can 187respond to the client, and this may take tens of seconds. 188Clients would have to wait too long if the key was regenerated every time. 189However, with small key sizes (e.g. 512) using 190.Nm 191from inetd may 192be feasible. 193.It Fl k Ar key_gen_time 194Specifies how often the ephemeral protocol version 1 server key is 195regenerated (default 3600 seconds, or one hour). 196The motivation for regenerating the key fairly 197often is that the key is not stored anywhere, and after about an hour 198it becomes impossible to recover the key for decrypting intercepted 199communications even if the machine is cracked into or physically 200seized. 201A value of zero indicates that the key will never be regenerated. 202.It Fl o Ar option 203Can be used to give options in the format used in the configuration file. 204This is useful for specifying options for which there is no separate 205command-line flag. 206For full details of the options, and their values, see 207.Xr sshd_config 5 . 208.It Fl p Ar port 209Specifies the port on which the server listens for connections 210(default 22). 211Multiple port options are permitted. 212Ports specified in the configuration file with the 213.Cm Port 214option are ignored when a command-line port is specified. 215Ports specified using the 216.Cm ListenAddress 217option override command-line ports. 218.It Fl q 219Quiet mode. 220Nothing is sent to the system log. 221Normally the beginning, 222authentication, and termination of each connection is logged. 223.It Fl T 224Extended test mode. 225Check the validity of the configuration file, output the effective configuration 226to stdout and then exit. 227Optionally, 228.Cm Match 229rules may be applied by specifying the connection parameters using one or more 230.Fl C 231options. 232.It Fl t 233Test mode. 234Only check the validity of the configuration file and sanity of the keys. 235This is useful for updating 236.Nm 237reliably as configuration options may change. 238.It Fl u Ar len 239This option is used to specify the size of the field 240in the 241.Li utmp 242structure that holds the remote host name. 243If the resolved host name is longer than 244.Ar len , 245the dotted decimal value will be used instead. 246This allows hosts with very long host names that 247overflow this field to still be uniquely identified. 248Specifying 249.Fl u0 250indicates that only dotted decimal addresses 251should be put into the 252.Pa utmp 253file. 254.Fl u0 255may also be used to prevent 256.Nm 257from making DNS requests unless the authentication 258mechanism or configuration requires it. 259Authentication mechanisms that may require DNS include 260.Cm RhostsRSAAuthentication , 261.Cm HostbasedAuthentication , 262and using a 263.Cm from="pattern-list" 264option in a key file. 265Configuration options that require DNS include using a 266USER@HOST pattern in 267.Cm AllowUsers 268or 269.Cm DenyUsers . 270.El 271.Sh AUTHENTICATION 272The OpenSSH SSH daemon supports SSH protocols 1 and 2. 273The default is to use protocol 2 only, 274though this can be changed via the 275.Cm Protocol 276option in 277.Xr sshd_config 5 . 278Protocol 2 supports DSA, ECDSA and RSA keys; 279protocol 1 only supports RSA keys. 280For both protocols, 281each host has a host-specific key, 282normally 2048 bits, 283used to identify the host. 284.Pp 285Forward security for protocol 1 is provided through 286an additional server key, 287normally 768 bits, 288generated when the server starts. 289This key is normally regenerated every hour if it has been used, and 290is never stored on disk. 291Whenever a client connects, the daemon responds with its public 292host and server keys. 293The client compares the 294RSA host key against its own database to verify that it has not changed. 295The client then generates a 256-bit random number. 296It encrypts this 297random number using both the host key and the server key, and sends 298the encrypted number to the server. 299Both sides then use this 300random number as a session key which is used to encrypt all further 301communications in the session. 302The rest of the session is encrypted 303using a conventional cipher, currently Blowfish or 3DES, with 3DES 304being used by default. 305The client selects the encryption algorithm 306to use from those offered by the server. 307.Pp 308For protocol 2, 309forward security is provided through a Diffie-Hellman key agreement. 310This key agreement results in a shared session key. 311The rest of the session is encrypted using a symmetric cipher, currently 312128-bit AES, Blowfish, 3DES, CAST128, Arcfour, 192-bit AES, or 256-bit AES. 313The client selects the encryption algorithm 314to use from those offered by the server. 315Additionally, session integrity is provided 316through a cryptographic message authentication code 317(hmac-md5, hmac-sha1, umac-64, hmac-ripemd160, 318hmac-sha2-256 or hmac-sha2-512). 319.Pp 320Finally, the server and the client enter an authentication dialog. 321The client tries to authenticate itself using 322host-based authentication, 323public key authentication, 324challenge-response authentication, 325or password authentication. 326.Pp 327Regardless of the authentication type, the account is checked to 328ensure that it is accessible. An account is not accessible if it is 329locked, listed in 330.Cm DenyUsers 331or its group is listed in 332.Cm DenyGroups 333\&. The definition of a locked account is system dependant. Some platforms 334have their own account database (eg AIX) and some modify the passwd field ( 335.Ql \&*LK\&* 336on Solaris and UnixWare, 337.Ql \&* 338on HP-UX, containing 339.Ql Nologin 340on Tru64, 341a leading 342.Ql \&*LOCKED\&* 343on FreeBSD and a leading 344.Ql \&! 345on most Linuxes). 346If there is a requirement to disable password authentication 347for the account while allowing still public-key, then the passwd field 348should be set to something other than these values (eg 349.Ql NP 350or 351.Ql \&*NP\&* 352). 353.Pp 354If the client successfully authenticates itself, a dialog for 355preparing the session is entered. 356At this time the client may request 357things like allocating a pseudo-tty, forwarding X11 connections, 358forwarding TCP connections, or forwarding the authentication agent 359connection over the secure channel. 360.Pp 361After this, the client either requests a shell or execution of a command. 362The sides then enter session mode. 363In this mode, either side may send 364data at any time, and such data is forwarded to/from the shell or 365command on the server side, and the user terminal in the client side. 366.Pp 367When the user program terminates and all forwarded X11 and other 368connections have been closed, the server sends command exit status to 369the client, and both sides exit. 370.Sh LOGIN PROCESS 371When a user successfully logs in, 372.Nm 373does the following: 374.Bl -enum -offset indent 375.It 376If the login is on a tty, and no command has been specified, 377prints last login time and 378.Pa /etc/motd 379(unless prevented in the configuration file or by 380.Pa ~/.hushlogin ; 381see the 382.Sx FILES 383section). 384.It 385If the login is on a tty, records login time. 386.It 387Checks 388.Pa /etc/nologin ; 389if it exists, prints contents and quits 390(unless root). 391.It 392Changes to run with normal user privileges. 393.It 394Sets up basic environment. 395.It 396Reads the file 397.Pa ~/.ssh/environment , 398if it exists, and users are allowed to change their environment. 399See the 400.Cm PermitUserEnvironment 401option in 402.Xr sshd_config 5 . 403.It 404Changes to user's home directory. 405.It 406If 407.Pa ~/.ssh/rc 408exists, runs it; else if 409.Pa /etc/ssh/sshrc 410exists, runs 411it; otherwise runs xauth. 412The 413.Dq rc 414files are given the X11 415authentication protocol and cookie in standard input. 416See 417.Sx SSHRC , 418below. 419.It 420Runs user's shell or command. 421.El 422.Sh SSHRC 423If the file 424.Pa ~/.ssh/rc 425exists, 426.Xr sh 1 427runs it after reading the 428environment files but before starting the user's shell or command. 429It must not produce any output on stdout; stderr must be used 430instead. 431If X11 forwarding is in use, it will receive the "proto cookie" pair in 432its standard input (and 433.Ev DISPLAY 434in its environment). 435The script must call 436.Xr xauth 1 437because 438.Nm 439will not run xauth automatically to add X11 cookies. 440.Pp 441The primary purpose of this file is to run any initialization routines 442which may be needed before the user's home directory becomes 443accessible; AFS is a particular example of such an environment. 444.Pp 445This file will probably contain some initialization code followed by 446something similar to: 447.Bd -literal -offset 3n 448if read proto cookie && [ -n "$DISPLAY" ]; then 449 if [ `echo $DISPLAY | cut -c1-10` = 'localhost:' ]; then 450 # X11UseLocalhost=yes 451 echo add unix:`echo $DISPLAY | 452 cut -c11-` $proto $cookie 453 else 454 # X11UseLocalhost=no 455 echo add $DISPLAY $proto $cookie 456 fi | xauth -q - 457fi 458.Ed 459.Pp 460If this file does not exist, 461.Pa /etc/ssh/sshrc 462is run, and if that 463does not exist either, xauth is used to add the cookie. 464.Sh AUTHORIZED_KEYS FILE FORMAT 465.Cm AuthorizedKeysFile 466specifies the files containing public keys for 467public key authentication; 468if none is specified, the default is 469.Pa ~/.ssh/authorized_keys 470and 471.Pa ~/.ssh/authorized_keys2 . 472Each line of the file contains one 473key (empty lines and lines starting with a 474.Ql # 475are ignored as 476comments). 477Protocol 1 public keys consist of the following space-separated fields: 478options, bits, exponent, modulus, comment. 479Protocol 2 public key consist of: 480options, keytype, base64-encoded key, comment. 481The options field is optional; 482its presence is determined by whether the line starts 483with a number or not (the options field never starts with a number). 484The bits, exponent, modulus, and comment fields give the RSA key for 485protocol version 1; the 486comment field is not used for anything (but may be convenient for the 487user to identify the key). 488For protocol version 2 the keytype is 489.Dq ecdsa-sha2-nistp256 , 490.Dq ecdsa-sha2-nistp384 , 491.Dq ecdsa-sha2-nistp521 , 492.Dq ssh-dss 493or 494.Dq ssh-rsa . 495.Pp 496Note that lines in this file are usually several hundred bytes long 497(because of the size of the public key encoding) up to a limit of 4988 kilobytes, which permits DSA keys up to 8 kilobits and RSA 499keys up to 16 kilobits. 500You don't want to type them in; instead, copy the 501.Pa identity.pub , 502.Pa id_dsa.pub , 503.Pa id_ecdsa.pub , 504or the 505.Pa id_rsa.pub 506file and edit it. 507.Pp 508.Nm 509enforces a minimum RSA key modulus size for protocol 1 510and protocol 2 keys of 768 bits. 511.Pp 512The options (if present) consist of comma-separated option 513specifications. 514No spaces are permitted, except within double quotes. 515The following option specifications are supported (note 516that option keywords are case-insensitive): 517.Bl -tag -width Ds 518.It Cm cert-authority 519Specifies that the listed key is a certification authority (CA) that is 520trusted to validate signed certificates for user authentication. 521.Pp 522Certificates may encode access restrictions similar to these key options. 523If both certificate restrictions and key options are present, the most 524restrictive union of the two is applied. 525.It Cm command="command" 526Specifies that the command is executed whenever this key is used for 527authentication. 528The command supplied by the user (if any) is ignored. 529The command is run on a pty if the client requests a pty; 530otherwise it is run without a tty. 531If an 8-bit clean channel is required, 532one must not request a pty or should specify 533.Cm no-pty . 534A quote may be included in the command by quoting it with a backslash. 535This option might be useful 536to restrict certain public keys to perform just a specific operation. 537An example might be a key that permits remote backups but nothing else. 538Note that the client may specify TCP and/or X11 539forwarding unless they are explicitly prohibited. 540The command originally supplied by the client is available in the 541.Ev SSH_ORIGINAL_COMMAND 542environment variable. 543Note that this option applies to shell, command or subsystem execution. 544Also note that this command may be superseded by either a 545.Xr sshd_config 5 546.Cm ForceCommand 547directive or a command embedded in a certificate. 548.It Cm environment="NAME=value" 549Specifies that the string is to be added to the environment when 550logging in using this key. 551Environment variables set this way 552override other default environment values. 553Multiple options of this type are permitted. 554Environment processing is disabled by default and is 555controlled via the 556.Cm PermitUserEnvironment 557option. 558This option is automatically disabled if 559.Cm UseLogin 560is enabled. 561.It Cm from="pattern-list" 562Specifies that in addition to public key authentication, either the canonical 563name of the remote host or its IP address must be present in the 564comma-separated list of patterns. 565See 566.Sx PATTERNS 567in 568.Xr ssh_config 5 569for more information on patterns. 570.Pp 571In addition to the wildcard matching that may be applied to hostnames or 572addresses, a 573.Cm from 574stanza may match IP addresses using CIDR address/masklen notation. 575.Pp 576The purpose of this option is to optionally increase security: public key 577authentication by itself does not trust the network or name servers or 578anything (but the key); however, if somebody somehow steals the key, the key 579permits an intruder to log in from anywhere in the world. 580This additional option makes using a stolen key more difficult (name 581servers and/or routers would have to be compromised in addition to 582just the key). 583.It Cm no-agent-forwarding 584Forbids authentication agent forwarding when this key is used for 585authentication. 586.It Cm no-port-forwarding 587Forbids TCP forwarding when this key is used for authentication. 588Any port forward requests by the client will return an error. 589This might be used, e.g. in connection with the 590.Cm command 591option. 592.It Cm no-pty 593Prevents tty allocation (a request to allocate a pty will fail). 594.It Cm no-user-rc 595Disables execution of 596.Pa ~/.ssh/rc . 597.It Cm no-X11-forwarding 598Forbids X11 forwarding when this key is used for authentication. 599Any X11 forward requests by the client will return an error. 600.It Cm permitopen="host:port" 601Limit local 602.Li ``ssh -L'' 603port forwarding such that it may only connect to the specified host and 604port. 605IPv6 addresses can be specified by enclosing the address in square brackets. 606Multiple 607.Cm permitopen 608options may be applied separated by commas. 609No pattern matching is performed on the specified hostnames, 610they must be literal domains or addresses. 611.It Cm principals="principals" 612On a 613.Cm cert-authority 614line, specifies allowed principals for certificate authentication as a 615comma-separated list. 616At least one name from the list must appear in the certificate's 617list of principals for the certificate to be accepted. 618This option is ignored for keys that are not marked as trusted certificate 619signers using the 620.Cm cert-authority 621option. 622.It Cm tunnel="n" 623Force a 624.Xr tun 4 625device on the server. 626Without this option, the next available device will be used if 627the client requests a tunnel. 628.El 629.Pp 630An example authorized_keys file: 631.Bd -literal -offset 3n 632# Comments allowed at start of line 633ssh-rsa AAAAB3Nza...LiPk== user@example.net 634from="*.sales.example.net,!pc.sales.example.net" ssh-rsa 635AAAAB2...19Q== john@example.net 636command="dump /home",no-pty,no-port-forwarding ssh-dss 637AAAAC3...51R== example.net 638permitopen="192.0.2.1:80",permitopen="192.0.2.2:25" ssh-dss 639AAAAB5...21S== 640tunnel="0",command="sh /etc/netstart tun0" ssh-rsa AAAA...== 641jane@example.net 642.Ed 643.Sh SSH_KNOWN_HOSTS FILE FORMAT 644The 645.Pa /etc/ssh/ssh_known_hosts 646and 647.Pa ~/.ssh/known_hosts 648files contain host public keys for all known hosts. 649The global file should 650be prepared by the administrator (optional), and the per-user file is 651maintained automatically: whenever the user connects from an unknown host, 652its key is added to the per-user file. 653.Pp 654Each line in these files contains the following fields: markers (optional), 655hostnames, bits, exponent, modulus, comment. 656The fields are separated by spaces. 657.Pp 658The marker is optional, but if it is present then it must be one of 659.Dq @cert-authority , 660to indicate that the line contains a certification authority (CA) key, 661or 662.Dq @revoked , 663to indicate that the key contained on the line is revoked and must not ever 664be accepted. 665Only one marker should be used on a key line. 666.Pp 667Hostnames is a comma-separated list of patterns 668.Pf ( Ql * 669and 670.Ql \&? 671act as 672wildcards); each pattern in turn is matched against the canonical host 673name (when authenticating a client) or against the user-supplied 674name (when authenticating a server). 675A pattern may also be preceded by 676.Ql \&! 677to indicate negation: if the host name matches a negated 678pattern, it is not accepted (by that line) even if it matched another 679pattern on the line. 680A hostname or address may optionally be enclosed within 681.Ql \&[ 682and 683.Ql \&] 684brackets then followed by 685.Ql \&: 686and a non-standard port number. 687.Pp 688Alternately, hostnames may be stored in a hashed form which hides host names 689and addresses should the file's contents be disclosed. 690Hashed hostnames start with a 691.Ql | 692character. 693Only one hashed hostname may appear on a single line and none of the above 694negation or wildcard operators may be applied. 695.Pp 696Bits, exponent, and modulus are taken directly from the RSA host key; they 697can be obtained, for example, from 698.Pa /etc/ssh/ssh_host_key.pub . 699The optional comment field continues to the end of the line, and is not used. 700.Pp 701Lines starting with 702.Ql # 703and empty lines are ignored as comments. 704.Pp 705When performing host authentication, authentication is accepted if any 706matching line has the proper key; either one that matches exactly or, 707if the server has presented a certificate for authentication, the key 708of the certification authority that signed the certificate. 709For a key to be trusted as a certification authority, it must use the 710.Dq @cert-authority 711marker described above. 712.Pp 713The known hosts file also provides a facility to mark keys as revoked, 714for example when it is known that the associated private key has been 715stolen. 716Revoked keys are specified by including the 717.Dq @revoked 718marker at the beginning of the key line, and are never accepted for 719authentication or as certification authorities, but instead will 720produce a warning from 721.Xr ssh 1 722when they are encountered. 723.Pp 724It is permissible (but not 725recommended) to have several lines or different host keys for the same 726names. 727This will inevitably happen when short forms of host names 728from different domains are put in the file. 729It is possible 730that the files contain conflicting information; authentication is 731accepted if valid information can be found from either file. 732.Pp 733Note that the lines in these files are typically hundreds of characters 734long, and you definitely don't want to type in the host keys by hand. 735Rather, generate them by a script, 736.Xr ssh-keyscan 1 737or by taking 738.Pa /etc/ssh/ssh_host_key.pub 739and adding the host names at the front. 740.Xr ssh-keygen 1 741also offers some basic automated editing for 742.Pa ~/.ssh/known_hosts 743including removing hosts matching a host name and converting all host 744names to their hashed representations. 745.Pp 746An example ssh_known_hosts file: 747.Bd -literal -offset 3n 748# Comments allowed at start of line 749closenet,...,192.0.2.53 1024 37 159...93 closenet.example.net 750cvs.example.net,192.0.2.10 ssh-rsa AAAA1234.....= 751# A hashed hostname 752|1|JfKTdBh7rNbXkVAQCRp4OQoPfmI=|USECr3SWf1JUPsms5AqfD5QfxkM= ssh-rsa 753AAAA1234.....= 754# A revoked key 755@revoked * ssh-rsa AAAAB5W... 756# A CA key, accepted for any host in *.mydomain.com or *.mydomain.org 757@cert-authority *.mydomain.org,*.mydomain.com ssh-rsa AAAAB5W... 758.Ed 759.Sh FILES 760.Bl -tag -width Ds -compact 761.It Pa ~/.hushlogin 762This file is used to suppress printing the last login time and 763.Pa /etc/motd , 764if 765.Cm PrintLastLog 766and 767.Cm PrintMotd , 768respectively, 769are enabled. 770It does not suppress printing of the banner specified by 771.Cm Banner . 772.Pp 773.It Pa ~/.rhosts 774This file is used for host-based authentication (see 775.Xr ssh 1 776for more information). 777On some machines this file may need to be 778world-readable if the user's home directory is on an NFS partition, 779because 780.Nm 781reads it as root. 782Additionally, this file must be owned by the user, 783and must not have write permissions for anyone else. 784The recommended 785permission for most machines is read/write for the user, and not 786accessible by others. 787.Pp 788.It Pa ~/.shosts 789This file is used in exactly the same way as 790.Pa .rhosts , 791but allows host-based authentication without permitting login with 792rlogin/rsh. 793.Pp 794.It Pa ~/.ssh/ 795This directory is the default location for all user-specific configuration 796and authentication information. 797There is no general requirement to keep the entire contents of this directory 798secret, but the recommended permissions are read/write/execute for the user, 799and not accessible by others. 800.Pp 801.It Pa ~/.ssh/authorized_keys 802Lists the public keys (DSA/ECDSA/RSA) that can be used for logging in 803as this user. 804The format of this file is described above. 805The content of the file is not highly sensitive, but the recommended 806permissions are read/write for the user, and not accessible by others. 807.Pp 808If this file, the 809.Pa ~/.ssh 810directory, or the user's home directory are writable 811by other users, then the file could be modified or replaced by unauthorized 812users. 813In this case, 814.Nm 815will not allow it to be used unless the 816.Cm StrictModes 817option has been set to 818.Dq no . 819.Pp 820.It Pa ~/.ssh/environment 821This file is read into the environment at login (if it exists). 822It can only contain empty lines, comment lines (that start with 823.Ql # ) , 824and assignment lines of the form name=value. 825The file should be writable 826only by the user; it need not be readable by anyone else. 827Environment processing is disabled by default and is 828controlled via the 829.Cm PermitUserEnvironment 830option. 831.Pp 832.It Pa ~/.ssh/known_hosts 833Contains a list of host keys for all hosts the user has logged into 834that are not already in the systemwide list of known host keys. 835The format of this file is described above. 836This file should be writable only by root/the owner and 837can, but need not be, world-readable. 838.Pp 839.It Pa ~/.ssh/rc 840Contains initialization routines to be run before 841the user's home directory becomes accessible. 842This file should be writable only by the user, and need not be 843readable by anyone else. 844.Pp 845.It Pa /etc/hosts.allow 846.It Pa /etc/hosts.deny 847Access controls that should be enforced by tcp-wrappers are defined here. 848Further details are described in 849.Xr hosts_access 5 . 850.Pp 851.It Pa /etc/hosts.equiv 852This file is for host-based authentication (see 853.Xr ssh 1 ) . 854It should only be writable by root. 855.Pp 856.It Pa /etc/moduli 857Contains Diffie-Hellman groups used for the "Diffie-Hellman Group Exchange". 858The file format is described in 859.Xr moduli 5 . 860.Pp 861.It Pa /etc/motd 862See 863.Xr motd 5 . 864.Pp 865.It Pa /etc/nologin 866If this file exists, 867.Nm 868refuses to let anyone except root log in. 869The contents of the file 870are displayed to anyone trying to log in, and non-root connections are 871refused. 872The file should be world-readable. 873.Pp 874.It Pa /etc/shosts.equiv 875This file is used in exactly the same way as 876.Pa hosts.equiv , 877but allows host-based authentication without permitting login with 878rlogin/rsh. 879.Pp 880.It Pa /etc/ssh/ssh_host_key 881.It Pa /etc/ssh/ssh_host_dsa_key 882.It Pa /etc/ssh/ssh_host_ecdsa_key 883.It Pa /etc/ssh/ssh_host_rsa_key 884These three files contain the private parts of the host keys. 885These files should only be owned by root, readable only by root, and not 886accessible to others. 887Note that 888.Nm 889does not start if these files are group/world-accessible. 890.Pp 891.It Pa /etc/ssh/ssh_host_key.pub 892.It Pa /etc/ssh/ssh_host_dsa_key.pub 893.It Pa /etc/ssh/ssh_host_ecdsa_key.pub 894.It Pa /etc/ssh/ssh_host_rsa_key.pub 895These three files contain the public parts of the host keys. 896These files should be world-readable but writable only by 897root. 898Their contents should match the respective private parts. 899These files are not 900really used for anything; they are provided for the convenience of 901the user so their contents can be copied to known hosts files. 902These files are created using 903.Xr ssh-keygen 1 . 904.Pp 905.It Pa /etc/ssh/ssh_known_hosts 906Systemwide list of known host keys. 907This file should be prepared by the 908system administrator to contain the public host keys of all machines in the 909organization. 910The format of this file is described above. 911This file should be writable only by root/the owner and 912should be world-readable. 913.Pp 914.It Pa /etc/ssh/sshd_config 915Contains configuration data for 916.Nm sshd . 917The file format and configuration options are described in 918.Xr sshd_config 5 . 919.Pp 920.It Pa /etc/ssh/sshrc 921Similar to 922.Pa ~/.ssh/rc , 923it can be used to specify 924machine-specific login-time initializations globally. 925This file should be writable only by root, and should be world-readable. 926.Pp 927.It Pa /var/empty 928.Xr chroot 2 929directory used by 930.Nm 931during privilege separation in the pre-authentication phase. 932The directory should not contain any files and must be owned by root 933and not group or world-writable. 934.Pp 935.It Pa /var/run/sshd.pid 936Contains the process ID of the 937.Nm 938listening for connections (if there are several daemons running 939concurrently for different ports, this contains the process ID of the one 940started last). 941The content of this file is not sensitive; it can be world-readable. 942.El 943.Sh SEE ALSO 944.Xr scp 1 , 945.Xr sftp 1 , 946.Xr ssh 1 , 947.Xr ssh-add 1 , 948.Xr ssh-agent 1 , 949.Xr ssh-keygen 1 , 950.Xr ssh-keyscan 1 , 951.Xr chroot 2 , 952.Xr hosts_access 5 , 953.Xr login.conf 5 , 954.Xr moduli 5 , 955.Xr sshd_config 5 , 956.Xr inetd 8 , 957.Xr sftp-server 8 958.Sh AUTHORS 959OpenSSH is a derivative of the original and free 960ssh 1.2.12 release by Tatu Ylonen. 961Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos, 962Theo de Raadt and Dug Song 963removed many bugs, re-added newer features and 964created OpenSSH. 965Markus Friedl contributed the support for SSH 966protocol versions 1.5 and 2.0. 967Niels Provos and Markus Friedl contributed support 968for privilege separation. 969.Sh CAVEATS 970System security is not improved unless 971.Nm rshd , 972.Nm rlogind , 973and 974.Nm rexecd 975are disabled (thus completely disabling 976.Xr rlogin 977and 978.Xr rsh 979into the machine). 980