Add the DragonFly cvs id and perform general cleanups on cvs/rcs/sccs ids. Most
[dragonfly.git] / crypto / openssh / sshd_config.5
CommitLineData
984263bc
MD
1.\" -*- nroff -*-
2.\"
3.\" Author: Tatu Ylonen <ylo@cs.hut.fi>
4.\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
5.\" All rights reserved
6.\"
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".
12.\"
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.
16.\"
17.\" Redistribution and use in source and binary forms, with or without
18.\" modification, are permitted provided that the following conditions
19.\" are met:
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.
25.\"
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.
36.\"
37.\" $OpenBSD: sshd_config.5,v 1.13 2002/09/16 20:12:11 stevesk Exp $
38.\" $FreeBSD: src/crypto/openssh/sshd_config.5,v 1.5.2.5 2003/02/11 12:11:54 des Exp $
1de703da 39.\" $DragonFly: src/crypto/openssh/Attic/sshd_config.5,v 1.2 2003/06/17 04:24:36 dillon Exp $
984263bc
MD
40.Dd September 25, 1999
41.Dt SSHD_CONFIG 5
42.Os
43.Sh NAME
44.Nm sshd_config
45.Nd OpenSSH SSH daemon configuration file
46.Sh SYNOPSIS
47.Bl -tag -width Ds -compact
48.It Pa /etc/ssh/sshd_config
49.El
50.Sh DESCRIPTION
51.Nm sshd
52reads configuration data from
53.Pa /etc/ssh/sshd_config
54(or the file specified with
55.Fl f
56on the command line).
57The file contains keyword-argument pairs, one per line.
58Lines starting with
59.Ql #
60and empty lines are interpreted as comments.
61.Pp
62The possible
63keywords and their meanings are as follows (note that
64keywords are case-insensitive and arguments are case-sensitive):
65.Bl -tag -width Ds
66.It Cm AFSTokenPassing
67Specifies whether an AFS token may be forwarded to the server.
68Default is
69.Dq no .
70.It Cm AllowGroups
71This keyword can be followed by a list of group name patterns, separated
72by spaces.
73If specified, login is allowed only for users whose primary
74group or supplementary group list matches one of the patterns.
75.Ql \&*
76and
77.Ql ?
78can be used as
79wildcards in the patterns.
80Only group names are valid; a numerical group ID is not recognized.
81By default, login is allowed for all groups.
82.Pp
83.It Cm AllowTcpForwarding
84Specifies whether TCP forwarding is permitted.
85The default is
86.Dq yes .
87Note that disabling TCP forwarding does not improve security unless
88users are also denied shell access, as they can always install their
89own forwarders.
90.Pp
91.It Cm AllowUsers
92This keyword can be followed by a list of user name patterns, separated
93by spaces.
94If specified, login is allowed only for users names that
95match one of the patterns.
96.Ql \&*
97and
98.Ql ?
99can be used as
100wildcards in the patterns.
101Only user names are valid; a numerical user ID is not recognized.
102By default, login is allowed for all users.
103If the pattern takes the form USER@HOST then USER and HOST
104are separately checked, restricting logins to particular
105users from particular hosts.
106.Pp
107.It Cm AuthorizedKeysFile
108Specifies the file that contains the public keys that can be used
109for user authentication.
110.Cm AuthorizedKeysFile
111may contain tokens of the form %T which are substituted during connection
112set-up. The following tokens are defined: %% is replaced by a literal '%',
113%h is replaced by the home directory of the user being authenticated and
114%u is replaced by the username of that user.
115After expansion,
116.Cm AuthorizedKeysFile
117is taken to be an absolute path or one relative to the user's home
118directory.
119The default is
120.Dq .ssh/authorized_keys .
121.It Cm Banner
122In some jurisdictions, sending a warning message before authentication
123may be relevant for getting legal protection.
124The contents of the specified file are sent to the remote user before
125authentication is allowed.
126This option is only available for protocol version 2.
127By default, no banner is displayed.
128.Pp
129.It Cm ChallengeResponseAuthentication
130Specifies whether challenge-response authentication is allowed.
131Specifically, in
132.Fx ,
133this controls the use of PAM (see
134.Xr pam 3 )
135for authentication.
136Note that this affects the effectiveness of the
137.Cm PasswordAuthentication
138and
139.Cm PermitRootLogin
140variables.
141The default is
142.Dq yes .
143.It Cm Ciphers
144Specifies the ciphers allowed for protocol version 2.
145Multiple ciphers must be comma-separated.
146The default is
147.Pp
148.Bd -literal
149 ``aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
150 aes192-cbc,aes256-cbc''
151.Ed
152.It Cm ClientAliveInterval
153Sets a timeout interval in seconds after which if no data has been received
154from the client,
155.Nm sshd
156will send a message through the encrypted
157channel to request a response from the client.
158The default
159is 0, indicating that these messages will not be sent to the client.
160This option applies to protocol version 2 only.
161.It Cm ClientAliveCountMax
162Sets the number of client alive messages (see above) which may be
163sent without
164.Nm sshd
165receiving any messages back from the client. If this threshold is
166reached while client alive messages are being sent,
167.Nm sshd
168will disconnect the client, terminating the session. It is important
169to note that the use of client alive messages is very different from
170.Cm KeepAlive
171(below). The client alive messages are sent through the
172encrypted channel and therefore will not be spoofable. The TCP keepalive
173option enabled by
174.Cm KeepAlive
175is spoofable. The client alive mechanism is valuable when the client or
176server depend on knowing when a connection has become inactive.
177.Pp
178The default value is 3. If
179.Cm ClientAliveInterval
180(above) is set to 15, and
181.Cm ClientAliveCountMax
182is left at the default, unresponsive ssh clients
183will be disconnected after approximately 45 seconds.
184.It Cm Compression
185Specifies whether compression is allowed.
186The argument must be
187.Dq yes
188or
189.Dq no .
190The default is
191.Dq yes .
192.It Cm DenyGroups
193This keyword can be followed by a list of group name patterns, separated
194by spaces.
195Login is disallowed for users whose primary group or supplementary
196group list matches one of the patterns.
197.Ql \&*
198and
199.Ql ?
200can be used as
201wildcards in the patterns.
202Only group names are valid; a numerical group ID is not recognized.
203By default, login is allowed for all groups.
204.Pp
205.It Cm DenyUsers
206This keyword can be followed by a list of user name patterns, separated
207by spaces.
208Login is disallowed for user names that match one of the patterns.
209.Ql \&*
210and
211.Ql ?
212can be used as wildcards in the patterns.
213Only user names are valid; a numerical user ID is not recognized.
214By default, login is allowed for all users.
215If the pattern takes the form USER@HOST then USER and HOST
216are separately checked, restricting logins to particular
217users from particular hosts.
218.It Cm GatewayPorts
219Specifies whether remote hosts are allowed to connect to ports
220forwarded for the client.
221By default,
222.Nm sshd
223binds remote port forwardings to the loopback address. This
224prevents other remote hosts from connecting to forwarded ports.
225.Cm GatewayPorts
226can be used to specify that
227.Nm sshd
228should bind remote port forwardings to the wildcard address,
229thus allowing remote hosts to connect to forwarded ports.
230The argument must be
231.Dq yes
232or
233.Dq no .
234The default is
235.Dq no .
236.It Cm HostbasedAuthentication
237Specifies whether rhosts or /etc/hosts.equiv authentication together
238with successful public key client host authentication is allowed
239(hostbased authentication).
240This option is similar to
241.Cm RhostsRSAAuthentication
242and applies to protocol version 2 only.
243The default is
244.Dq no .
245.It Cm HostKey
246Specifies a file containing a private host key
247used by SSH.
248The default is
249.Pa /etc/ssh/ssh_host_key
250for protocol version 1, and
251.Pa /etc/ssh/ssh_host_dsa_key
252for protocol version 2.
253Note that
254.Nm sshd
255will refuse to use a file if it is group/world-accessible.
256It is possible to have multiple host key files.
257.Dq rsa1
258keys are used for version 1 and
259.Dq dsa
260or
261.Dq rsa
262are used for version 2 of the SSH protocol.
263.It Cm IgnoreRhosts
264Specifies that
265.Pa .rhosts
266and
267.Pa .shosts
268files will not be used in
269.Cm RhostsAuthentication ,
270.Cm RhostsRSAAuthentication
271or
272.Cm HostbasedAuthentication .
273.Pp
274.Pa /etc/hosts.equiv
275and
276.Pa /etc/ssh/shosts.equiv
277are still used.
278The default is
279.Dq yes .
280.It Cm IgnoreUserKnownHosts
281Specifies whether
282.Nm sshd
283should ignore the user's
284.Pa $HOME/.ssh/known_hosts
285during
286.Cm RhostsRSAAuthentication
287or
288.Cm HostbasedAuthentication .
289The default is
290.Dq no .
291.It Cm KeepAlive
292Specifies whether the system should send TCP keepalive messages to the
293other side.
294If they are sent, death of the connection or crash of one
295of the machines will be properly noticed.
296However, this means that
297connections will die if the route is down temporarily, and some people
298find it annoying.
299On the other hand, if keepalives are not sent,
300sessions may hang indefinitely on the server, leaving
301.Dq ghost
302users and consuming server resources.
303.Pp
304The default is
305.Dq yes
306(to send keepalives), and the server will notice
307if the network goes down or the client host crashes.
308This avoids infinitely hanging sessions.
309.Pp
310To disable keepalives, the value should be set to
311.Dq no .
312.It Cm KerberosAuthentication
313Specifies whether Kerberos authentication is allowed.
314This can be in the form of a Kerberos ticket, or if
315.Cm PasswordAuthentication
316is yes, the password provided by the user will be validated through
317the Kerberos KDC.
318To use this option, the server needs a
319Kerberos servtab which allows the verification of the KDC's identity.
320Default is
321.Dq no .
322.It Cm KerberosOrLocalPasswd
323If set then if password authentication through Kerberos fails then
324the password will be validated via any additional local mechanism
325such as
326.Pa /etc/passwd .
327Default is
328.Dq yes .
329.It Cm KerberosTgtPassing
330Specifies whether a Kerberos TGT may be forwarded to the server.
331Default is
332.Dq no ,
333as this only works when the Kerberos KDC is actually an AFS kaserver.
334.It Cm KerberosTicketCleanup
335Specifies whether to automatically destroy the user's ticket cache
336file on logout.
337Default is
338.Dq yes .
339.It Cm KeyRegenerationInterval
340In protocol version 1, the ephemeral server key is automatically regenerated
341after this many seconds (if it has been used).
342The purpose of regeneration is to prevent
343decrypting captured sessions by later breaking into the machine and
344stealing the keys.
345The key is never stored anywhere.
346If the value is 0, the key is never regenerated.
347The default is 3600 (seconds).
348.It Cm ListenAddress
349Specifies the local addresses
350.Nm sshd
351should listen on.
352The following forms may be used:
353.Pp
354.Bl -item -offset indent -compact
355.It
356.Cm ListenAddress
357.Sm off
358.Ar host No | Ar IPv4_addr No | Ar IPv6_addr
359.Sm on
360.It
361.Cm ListenAddress
362.Sm off
363.Ar host No | Ar IPv4_addr No : Ar port
364.Sm on
365.It
366.Cm ListenAddress
367.Sm off
368.Oo
369.Ar host No | Ar IPv6_addr Oc : Ar port
370.Sm on
371.El
372.Pp
373If
374.Ar port
375is not specified,
376.Nm sshd
377will listen on the address and all prior
378.Cm Port
379options specified. The default is to listen on all local
380addresses. Multiple
381.Cm ListenAddress
382options are permitted. Additionally, any
383.Cm Port
384options must precede this option for non port qualified addresses.
385.It Cm LoginGraceTime
386The server disconnects after this time if the user has not
387successfully logged in.
388If the value is 0, there is no time limit.
389The default is 120 seconds.
390.It Cm LogLevel
391Gives the verbosity level that is used when logging messages from
392.Nm sshd .
393The possible values are:
394QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2 and DEBUG3.
395The default is INFO. DEBUG and DEBUG1 are equivalent. DEBUG2
396and DEBUG3 each specify higher levels of debugging output.
397Logging with a DEBUG level violates the privacy of users
398and is not recommended.
399.It Cm MACs
400Specifies the available MAC (message authentication code) algorithms.
401The MAC algorithm is used in protocol version 2
402for data integrity protection.
403Multiple algorithms must be comma-separated.
404The default is
405.Dq hmac-md5,hmac-sha1,hmac-ripemd160,hmac-sha1-96,hmac-md5-96 .
406.It Cm MaxStartups
407Specifies the maximum number of concurrent unauthenticated connections to the
408.Nm sshd
409daemon.
410Additional connections will be dropped until authentication succeeds or the
411.Cm LoginGraceTime
412expires for a connection.
413The default is 10.
414.Pp
415Alternatively, random early drop can be enabled by specifying
416the three colon separated values
417.Dq start:rate:full
418(e.g., "10:30:60").
419.Nm sshd
420will refuse connection attempts with a probability of
421.Dq rate/100
422(30%)
423if there are currently
424.Dq start
425(10)
426unauthenticated connections.
427The probability increases linearly and all connection attempts
428are refused if the number of unauthenticated connections reaches
429.Dq full
430(60).
431.It Cm PasswordAuthentication
432Specifies whether password authentication is allowed.
433The default is
434.Dq yes .
435Note that
436.Cm ChallengeResponseAuthentication
437is
438.Dq yes ,
439and the PAM authentication policy for
440.Nm sshd
441includes
442.Xr pam_unix 8 ,
443password authentication will be allowed through the challenge-response
444mechanism regardless of the value of
445.Cm PasswordAuthentication .
446.It Cm PermitEmptyPasswords
447When password authentication is allowed, it specifies whether the
448server allows login to accounts with empty password strings.
449The default is
450.Dq no .
451.It Cm PermitRootLogin
452Specifies whether root can login using
453.Xr ssh 1 .
454The argument must be
455.Dq yes ,
456.Dq without-password ,
457.Dq forced-commands-only
458or
459.Dq no .
460The default is
461.Dq no .
462Note that if
463.Cm ChallengeResponseAuthentication
464is
465.Dq yes ,
466the root user may be allowed in with its password even if
467.Cm PermitRootLogin is set to
468.Dq without-password .
469.Pp
470If this option is set to
471.Dq without-password
472password authentication is disabled for root.
473.Pp
474If this option is set to
475.Dq forced-commands-only
476root login with public key authentication will be allowed,
477but only if the
478.Ar command
479option has been specified
480(which may be useful for taking remote backups even if root login is
481normally not allowed). All other authentication methods are disabled
482for root.
483.Pp
484If this option is set to
485.Dq no
486root is not allowed to login.
487.It Cm PermitUserEnvironment
488Specifies whether
489.Pa ~/.ssh/environment
490and
491.Cm environment=
492options in
493.Pa ~/.ssh/authorized_keys
494are processed by
495.Nm sshd .
496The default is
497.Dq no .
498Enabling environment processing may enable users to bypass access
499restrictions in some configurations using mechanisms such as
500.Ev LD_PRELOAD .
501.It Cm PidFile
502Specifies the file that contains the process ID of the
503.Nm sshd
504daemon.
505The default is
506.Pa /var/run/sshd.pid .
507.It Cm Port
508Specifies the port number that
509.Nm sshd
510listens on.
511The default is 22.
512Multiple options of this type are permitted.
513See also
514.Cm ListenAddress .
515.It Cm PrintLastLog
516Specifies whether
517.Nm sshd
518should print the date and time when the user last logged in.
519The default is
520.Dq yes .
521.It Cm PrintMotd
522Specifies whether
523.Nm sshd
524should print
525.Pa /etc/motd
526when a user logs in interactively.
527(On some systems it is also printed by the shell,
528.Pa /etc/profile ,
529or equivalent.)
530The default is
531.Dq yes .
532.It Cm Protocol
533Specifies the protocol versions
534.Nm sshd
535supports.
536The possible values are
537.Dq 1
538and
539.Dq 2 .
540Multiple versions must be comma-separated.
541The default is
542.Dq 2,1 .
543Note that the order of the protocol list does not indicate preference,
544because the client selects among multiple protocol versions offered
545by the server.
546Specifying
547.Dq 2,1
548is identical to
549.Dq 1,2 .
550.It Cm PubkeyAuthentication
551Specifies whether public key authentication is allowed.
552The default is
553.Dq yes .
554Note that this option applies to protocol version 2 only.
555.It Cm RhostsAuthentication
556Specifies whether authentication using rhosts or
557.Pa /etc/hosts.equiv
558files is sufficient.
559Normally, this method should not be permitted because it is insecure.
560.Cm RhostsRSAAuthentication
561should be used
562instead, because it performs RSA-based host authentication in addition
563to normal rhosts or
564.Pa /etc/hosts.equiv
565authentication.
566The default is
567.Dq no .
568This option applies to protocol version 1 only.
569.It Cm RhostsRSAAuthentication
570Specifies whether rhosts or
571.Pa /etc/hosts.equiv
572authentication together
573with successful RSA host authentication is allowed.
574The default is
575.Dq no .
576This option applies to protocol version 1 only.
577.It Cm RSAAuthentication
578Specifies whether pure RSA authentication is allowed.
579The default is
580.Dq yes .
581This option applies to protocol version 1 only.
582.It Cm ServerKeyBits
583Defines the number of bits in the ephemeral protocol version 1 server key.
584The minimum value is 512, and the default is 768.
585.It Cm StrictModes
586Specifies whether
587.Nm sshd
588should check file modes and ownership of the
589user's files and home directory before accepting login.
590This is normally desirable because novices sometimes accidentally leave their
591directory or files world-writable.
592The default is
593.Dq yes .
594.It Cm Subsystem
595Configures an external subsystem (e.g., file transfer daemon).
596Arguments should be a subsystem name and a command to execute upon subsystem
597request.
598The command
599.Xr sftp-server 8
600implements the
601.Dq sftp
602file transfer subsystem.
603By default no subsystems are defined.
604Note that this option applies to protocol version 2 only.
605.It Cm SyslogFacility
606Gives the facility code that is used when logging messages from
607.Nm sshd .
608The possible values are: DAEMON, USER, AUTH, LOCAL0, LOCAL1, LOCAL2,
609LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.
610The default is AUTH.
611.It Cm UseLogin
612Specifies whether
613.Xr login 1
614is used for interactive login sessions.
615The default is
616.Dq no .
617Note that
618.Xr login 1
619is never used for remote command execution.
620Note also, that if this is enabled,
621.Cm X11Forwarding
622will be disabled because
623.Xr login 1
624does not know how to handle
625.Xr xauth 1
626cookies. If
627.Cm UsePrivilegeSeparation
628is specified, it will be disabled after authentication.
629.It Cm UsePrivilegeSeparation
630Specifies whether
631.Nm sshd
632separates privileges by creating an unprivileged child process
633to deal with incoming network traffic. After successful authentication,
634another process will be created that has the privilege of the authenticated
635user. The goal of privilege separation is to prevent privilege
636escalation by containing any corruption within the unprivileged processes.
637The default is
638.Dq yes .
639.It Cm VerifyReverseMapping
640Specifies whether
641.Nm sshd
642should try to verify the remote host name and check that
643the resolved host name for the remote IP address maps back to the
644very same IP address.
645The default is
646.Dq no .
647.It Cm VersionAddendum
648Specifies a string to append to the regular version string to identify
649OS- or site-specific modifications.
650The default is
651.Dq FreeBSD-20030201 .
652.It Cm X11DisplayOffset
653Specifies the first display number available for
654.Nm sshd Ns 's
655X11 forwarding.
656This prevents
657.Nm sshd
658from interfering with real X11 servers.
659The default is 10.
660.It Cm X11Forwarding
661Specifies whether X11 forwarding is permitted.
662The argument must be
663.Dq yes
664or
665.Dq no .
666The default is
667.Dq yes .
668.Pp
669When X11 forwarding is enabled, there may be additional exposure to
670the server and to client displays if the
671.Nm sshd
672proxy display is configured to listen on the wildcard address (see
673.Cm X11UseLocalhost
674below), however this is not the default.
675Additionally, the authentication spoofing and authentication data
676verification and substitution occur on the client side.
677The security risk of using X11 forwarding is that the client's X11
678display server may be exposed to attack when the ssh client requests
679forwarding (see the warnings for
680.Cm ForwardX11
681in
682.Xr ssh_config 5 ).
683A system administrator may have a stance in which they want to
684protect clients that may expose themselves to attack by unwittingly
685requesting X11 forwarding, which can warrant a
686.Dq no
687setting.
688.Pp
689Note that disabling X11 forwarding does not prevent users from
690forwarding X11 traffic, as users can always install their own forwarders.
691X11 forwarding is automatically disabled if
692.Cm UseLogin
693is enabled.
694.It Cm X11UseLocalhost
695Specifies whether
696.Nm sshd
697should bind the X11 forwarding server to the loopback address or to
698the wildcard address. By default,
699.Nm sshd
700binds the forwarding server to the loopback address and sets the
701hostname part of the
702.Ev DISPLAY
703environment variable to
704.Dq localhost .
705This prevents remote hosts from connecting to the proxy display.
706However, some older X11 clients may not function with this
707configuration.
708.Cm X11UseLocalhost
709may be set to
710.Dq no
711to specify that the forwarding server should be bound to the wildcard
712address.
713The argument must be
714.Dq yes
715or
716.Dq no .
717The default is
718.Dq yes .
719.It Cm XAuthLocation
720Specifies the full pathname of the
721.Xr xauth 1
722program.
723The default is
724.Pa /usr/X11R6/bin/xauth .
725.El
726.Ss Time Formats
727.Pp
728.Nm sshd
729command-line arguments and configuration file options that specify time
730may be expressed using a sequence of the form:
731.Sm off
732.Ar time Op Ar qualifier ,
733.Sm on
734where
735.Ar time
736is a positive integer value and
737.Ar qualifier
738is one of the following:
739.Pp
740.Bl -tag -width Ds -compact -offset indent
741.It Cm <none>
742seconds
743.It Cm s | Cm S
744seconds
745.It Cm m | Cm M
746minutes
747.It Cm h | Cm H
748hours
749.It Cm d | Cm D
750days
751.It Cm w | Cm W
752weeks
753.El
754.Pp
755Each member of the sequence is added together to calculate
756the total time value.
757.Pp
758Time format examples:
759.Pp
760.Bl -tag -width Ds -compact -offset indent
761.It 600
762600 seconds (10 minutes)
763.It 10m
76410 minutes
765.It 1h30m
7661 hour 30 minutes (90 minutes)
767.El
768.Sh FILES
769.Bl -tag -width Ds
770.It Pa /etc/ssh/sshd_config
771Contains configuration data for
772.Nm sshd .
773This file should be writable by root only, but it is recommended
774(though not necessary) that it be world-readable.
775.El
776.Sh AUTHORS
777OpenSSH is a derivative of the original and free
778ssh 1.2.12 release by Tatu Ylonen.
779Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
780Theo de Raadt and Dug Song
781removed many bugs, re-added newer features and
782created OpenSSH.
783Markus Friedl contributed the support for SSH
784protocol versions 1.5 and 2.0.
785Niels Provos and Markus Friedl contributed support
786for privilege separation.
787.Sh SEE ALSO
788.Xr sshd 8