SSHD_CONFIG(5)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 BSD File Formats Manual\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SSHD_CONFIG(5)<\/p>\n
NAME<\/p>\n
sshd_config \u2014 OpenSSH SSH daemon configuration file<\/p>\n
SYNOPSIS<\/p>\n
\/etc\/ssh\/sshd_config<\/p>\n
DESCRIPTION<\/p>\n
sshd(8) reads configuration data from \/etc\/ssh\/sshd_config (or the file
\nspecified with -f on the command line).\u00a0 The file contains keyword-
\nargument pairs, one per line.\u00a0 Lines starting with \u2018#\u2019 and empty lines
\nare interpreted as comments.\u00a0 Arguments may optionally be enclosed in
\ndouble quotes (“) in order to represent arguments containing spaces.<\/p>\n
The possible keywords and their meanings are as follows (note that key\u2010
\nwords are case-insensitive and arguments are case-sensitive):<\/p>\n
AcceptEnv
\nSpecifies what environment variables sent by the client will be
\ncopied into the session’s environ(7).\u00a0 See SendEnv in
\nssh_config(5) for how to configure the client.\u00a0 Note that envi\u2010
\nronment passing is only supported for protocol 2.\u00a0 Variables
\nare specified by name, which may contain the wildcard charac\u2010
\nters \u2018*\u2019 and \u2018?\u2019.\u00a0 Multiple environment variables may be sepa\u2010
\nrated by whitespace or spread across multiple AcceptEnv direc\u2010
\ntives.\u00a0 Be warned that some environment variables could be used
\nto bypass restricted user environments.\u00a0 For this reason, care
\nshould be taken in the use of this directive.\u00a0 The default is
\nnot to accept any environment variables.<\/p>\n
AddressFamily
\nSpecifies which address family should be used by sshd(8).
\nValid arguments are \u201cany\u201d, \u201cinet\u201d (use IPv4 only), or \u201cinet6\u201d
\n(use IPv6 only).\u00a0 The default is \u201cany\u201d.<\/p>\n
AllowAgentForwarding
\nSpecifies whether ssh-agent(1) forwarding is permitted.\u00a0 The
\ndefault is \u201cyes\u201d.\u00a0 Note that disabling agent forwarding does
\nnot improve security unless users are also denied shell access,
\nas they can always install their own forwarders.<\/p>\n
AllowGroups
\nThis keyword can be followed by a list of group name patterns,
\nseparated by spaces.\u00a0 If specified, login is allowed only for
\nusers whose primary group or supplementary group list matches
\none of the patterns.\u00a0 Only group names are valid; a numerical
\ngroup ID is not recognized.\u00a0 By default, login is allowed for
\nall groups.\u00a0 The allow\/deny directives are processed in the
\nfollowing order: DenyUsers, AllowUsers, DenyGroups, and finally
\nAllowGroups.<\/p>\n
See PATTERNS in ssh_config(5) for more information on patterns.<\/p>\n
AllowTcpForwarding
\nSpecifies whether TCP forwarding is permitted.\u00a0 The available
\noptions are \u201cyes\u201d or \u201call\u201d to allow TCP forwarding, \u201cno\u201d to
\nprevent all TCP forwarding, \u201clocal\u201d to allow local (from the
\nperspective of ssh(1)) forwarding only or \u201cremote\u201d to allow
\nremote forwarding only.\u00a0 The default is \u201cyes\u201d.\u00a0 Note that dis\u2010
\nabling TCP forwarding does not improve security unless users
\nare also denied shell access, as they can always install their
\nown forwarders.<\/p>\n
AllowStreamLocalForwarding
\nSpecifies whether StreamLocal (Unix-domain socket) forwarding
\nis permitted.\u00a0 The available options are \u201cyes\u201d or \u201call\u201d to
\nallow StreamLocal forwarding, \u201cno\u201d to prevent all StreamLocal
\nforwarding, \u201clocal\u201d to allow local (from the perspective of
\nssh(1)) forwarding only or \u201cremote\u201d to allow remote forwarding
\nonly.\u00a0 The default is \u201cyes\u201d.\u00a0 Note that disabling StreamLocal
\nforwarding does not improve security unless users are also
\ndenied shell access, as they can always install their own for\u2010
\nwarders.<\/p>\n
AllowUsers
\nThis keyword can be followed by a list of user name patterns,
\nseparated by spaces.\u00a0 If specified, login is allowed only for
\nuser names that match one of the patterns.\u00a0 Only user names are
\nvalid; a numerical user ID is not recognized.\u00a0 By default,
\nlogin is allowed for all users.\u00a0 If the pattern takes the form
\nUSER@HOST\u00a0then USER and HOST are separately checked, restrict\u2010
\ning logins to particular users from particular hosts.\u00a0 The
\nallow\/deny directives are processed in the following order:
\nDenyUsers, AllowUsers, DenyGroups, and finally AllowGroups.<\/p>\n
See PATTERNS in ssh_config(5) for more information on patterns.<\/p>\n
AuthenticationMethods
\nSpecifies the authentication methods that must be successfully
\ncompleted for a user to be granted access.\u00a0 This option must be
\nfollowed by one or more comma-separated lists of authentication
\nmethod names.\u00a0 Successful authentication requires completion of
\nevery method in at least one of these lists.<\/p>\n
For example, an argument of \u201cpublickey,password
\npublickey,keyboard-interactive\u201d would require the user to com\u2010
\nplete public key authentication, followed by either password or
\nkeyboard interactive authentication.\u00a0 Only methods that are
\nnext in one or more lists are offered at each stage, so for
\nthis example, it would not be possible to attempt password or
\nkeyboard-interactive authentication before public key.<\/p>\n
For keyboard interactive authentication it is also possible to
\nrestrict authentication to a specific device by appending a
\ncolon followed by the device identifier \u201cbsdauth\u201d, \u201cpam\u201d, or
\n\u201cskey\u201d, depending on the server configuration.\u00a0 For example,
\n\u201ckeyboard-interactive:bsdauth\u201d would restrict keyboard interac\u2010
\ntive authentication to the \u201cbsdauth\u201d device.<\/p>\n
This option is only available for SSH protocol 2 and will yield
\na fatal error if enabled if protocol 1 is also enabled.\u00a0 Note
\nthat each authentication method listed should also be explic\u2010
\nitly enabled in the configuration.\u00a0 The default is not to
\nrequire multiple authentication; successful completion of a
\nsingle authentication method is sufficient.<\/p>\n
AuthorizedKeysCommand
\nSpecifies a program to be used to look up the user’s public
\nkeys.\u00a0 The program must be owned by root and not writable by
\ngroup or others.\u00a0 It will be invoked with a single argument of
\nthe username being authenticated, and should produce on stan\u2010
\ndard output zero or more lines of authorized_keys output (see
\nAUTHORIZED_KEYS in sshd(8)).\u00a0 If a key supplied by Authorized\u2010
\nKeysCommand does not successfully authenticate and authorize
\nthe user then public key authentication continues using the
\nusual AuthorizedKeysFile files.\u00a0 By default, no Authorized\u2010
\nKeysCommand is run.<\/p>\n
AuthorizedKeysCommandUser
\nSpecifies the user under whose account the AuthorizedKeysCom\u2010
\nmand is run.\u00a0 It is recommended to use a dedicated user that
\nhas no other role on the host than running authorized keys com\u2010
\nmands.<\/p>\n
AuthorizedKeysFile
\nSpecifies the file that contains the public keys that can be
\nused for user authentication.\u00a0 The format is described in the
\nAUTHORIZED_KEYS FILE FORMAT section of sshd(8).
\nAuthorizedKeysFile may contain tokens of the form %T which are
\nsubstituted during connection setup.\u00a0 The following tokens are
\ndefined: %% is replaced by a literal ‘%’, %h is replaced by the
\nhome directory of the user being authenticated, and %u is
\nreplaced by the username of that user.\u00a0 After expansion,
\nAuthorizedKeysFile is taken to be an absolute path or one rela\u2010
\ntive to the user’s home directory.\u00a0 Multiple files may be
\nlisted, separated by whitespace.\u00a0 The default is
\n\u201c.ssh\/authorized_keys .ssh\/authorized_keys2\u201d.<\/p>\n
AuthorizedPrincipalsFile
\nSpecifies a file that lists principal names that are accepted
\nfor certificate authentication.\u00a0 When using certificates signed
\nby a key listed in TrustedUserCAKeys, this file lists names,
\none of which must appear in the certificate for it to be
\naccepted for authentication.\u00a0 Names are listed one per line
\npreceded by key options (as described in AUTHORIZED_KEYS FILE
\nFORMAT in sshd(8)).\u00a0 Empty lines and comments starting with \u2018#\u2019
\nare ignored.<\/p>\n
AuthorizedPrincipalsFile may contain tokens of the form %T
\nwhich are substituted during connection setup.\u00a0 The following
\ntokens are defined: %% is replaced by a literal ‘%’, %h is
\nreplaced by the home directory of the user being authenticated,
\nand %u is replaced by the username of that user.\u00a0 After expan\u2010
\nsion, AuthorizedPrincipalsFile is taken to be an absolute path
\nor one relative to the user’s home directory.<\/p>\n
The default is \u201cnone\u201d, i.e. not to use a principals file \u2013 in
\nthis case, the username of the user must appear in a certifi\u2010
\ncate’s principals list for it to be accepted.\u00a0 Note that
\nAuthorizedPrincipalsFile is only used when authentication pro\u2010
\nceeds using a CA listed in TrustedUserCAKeys and is not con\u2010
\nsulted for certification authorities trusted via
\n~\/.ssh\/authorized_keys, though the principals= key option
\noffers a similar facility (see sshd(8) for details).<\/p>\n
Banner\u00a0 The contents of the specified file are sent to the remote user
\nbefore authentication is allowed.\u00a0 If the argument is \u201cnone\u201d
\nthen no banner is displayed.\u00a0 This option is only available for
\nprotocol version 2.\u00a0 By default, no banner is displayed.<\/p>\n
ChallengeResponseAuthentication
\nSpecifies whether challenge-response authentication is allowed
\n(e.g. via PAM or through authentication styles supported in
\nlogin.conf(5)) The default is \u201cyes\u201d.<\/p>\n
ChrootDirectory
\nSpecifies the pathname of a directory to chroot(2) to after
\nauthentication.\u00a0 All components of the pathname must be root-
\nowned directories that are not writable by any other user or
\ngroup.\u00a0 After the chroot, sshd(8) changes the working directory
\nto the user’s home directory.<\/p>\n
The pathname may contain the following tokens that are expanded
\nat runtime once the connecting user has been authenticated: %%
\nis replaced by a literal ‘%’, %h is replaced by the home direc\u2010
\ntory of the user being authenticated, and %u is replaced by the
\nusername of that user.<\/p>\n
The ChrootDirectory must contain the necessary files and direc\u2010
\ntories to support the user’s session.\u00a0 For an interactive ses\u2010
\nsion this requires at least a shell, typically sh(1), and basic
\n\/dev nodes such as null(4), zero(4), stdin(4), stdout(4),
\nstderr(4), arandom(4) and tty(4) devices.\u00a0 For file transfer
\nsessions using \u201csftp\u201d, no additional configuration of the envi\u2010
\nronment is necessary if the in-process sftp server is used,
\nthough sessions which use logging may require \/dev\/log inside
\nthe chroot directory on some operating systems (see
\nsftp-server(8) for details).<\/p>\n
The default is not to chroot(2).<\/p>\n
Ciphers
\nSpecifies the ciphers allowed for protocol version 2.\u00a0 Multiple
\nciphers must be comma-separated.\u00a0 The supported ciphers are:<\/p>\n
3des-cbc
\naes128-cbc
\naes192-cbc
\naes256-cbc
\naes128-ctr
\naes192-ctr
\naes256-ctr
\naes128-gcm@openssh.com
\naes256-gcm@openssh.com
\narcfour
\narcfour128
\narcfour256
\nblowfish-cbc
\ncast128-cbc
\nchacha20-poly1305@openssh.com<\/p>\n
The default is:<\/p>\n
aes128-ctr,aes192-ctr,aes256-ctr,
\naes128-gcm@openssh.com,aes256-gcm@openssh.com,
\nchacha20-poly1305@openssh.com<\/p>\n
The list of available ciphers may also be obtained using the -Q
\noption of ssh(1).<\/p>\n
ClientAliveCountMax
\nSets the number of client alive messages (see below) which may
\nbe sent without sshd(8) receiving any messages back from the
\nclient.\u00a0 If this threshold is reached while client alive mes\u2010
\nsages are being sent, sshd will disconnect the client, termi\u2010
\nnating the session.\u00a0 It is important to note that the use of
\nclient alive messages is very different from TCPKeepAlive
\n(below).\u00a0 The client alive messages are sent through the
\nencrypted channel and therefore will not be spoofable.\u00a0 The TCP
\nkeepalive option enabled by TCPKeepAlive is spoofable.\u00a0 The
\nclient alive mechanism is valuable when the client or server
\ndepend on knowing when a connection has become inactive.<\/p>\n
The default value is 3.\u00a0 If ClientAliveInterval (see below) is
\nset to 15, and ClientAliveCountMax is left at the default,
\nunresponsive SSH clients will be disconnected after approxi\u2010
\nmately 45 seconds.\u00a0 This option applies to protocol version 2
\nonly.<\/p>\n
ClientAliveInterval
\nSets a timeout interval in seconds after which if no data has
\nbeen received from the client, sshd(8) will send a message
\nthrough the encrypted channel to request a response from the
\nclient.\u00a0 The default is 0, indicating that these messages will
\nnot be sent to the client.\u00a0 This option applies to protocol
\nversion 2 only.<\/p>\n
Compression
\nSpecifies whether compression is allowed, or delayed until the
\nuser has authenticated successfully.\u00a0 The argument must be
\n\u201cyes\u201d, \u201cdelayed\u201d, or \u201cno\u201d.\u00a0 The default is \u201cdelayed\u201d.<\/p>\n
DenyGroups
\nThis keyword can be followed by a list of group name patterns,
\nseparated by spaces.\u00a0 Login is disallowed for users whose pri\u2010
\nmary group or supplementary group list matches one of the pat\u2010
\nterns.\u00a0 Only group names are valid; a numerical group ID is not
\nrecognized.\u00a0 By default, login is allowed for all groups.\u00a0 The
\nallow\/deny directives are processed in the following order:
\nDenyUsers, AllowUsers, DenyGroups, and finally AllowGroups.<\/p>\n
See PATTERNS in ssh_config(5) for more information on patterns.<\/p>\n
DenyUsers
\nThis keyword can be followed by a list of user name patterns,
\nseparated by spaces.\u00a0 Login is disallowed for user names that
\nmatch one of the patterns.\u00a0 Only user names are valid; a numer\u2010
\nical user ID is not recognized.\u00a0 By default, login is allowed
\nfor all users.\u00a0 If the pattern takes the form\u00a0USER@HOST\u00a0then
\nUSER and HOST are separately checked, restricting logins to
\nparticular users from particular hosts.\u00a0 The allow\/deny direc\u2010
\ntives are processed in the following order: DenyUsers,
\nAllowUsers, DenyGroups, and finally AllowGroups.<\/p>\n
See PATTERNS in ssh_config(5) for more information on patterns.<\/p>\n
ForceCommand
\nForces the execution of the command specified by ForceCommand,
\nignoring any command supplied by the client and ~\/.ssh\/rc if
\npresent.\u00a0 The command is invoked by using the user’s login
\nshell with the -c option.\u00a0 This applies to shell, command, or
\nsubsystem execution.\u00a0 It is most useful inside a Match block.
\nThe command originally supplied by the client is available in
\nthe SSH_ORIGINAL_COMMAND environment variable.\u00a0 Specifying a
\ncommand of \u201cinternal-sftp\u201d will force the use of an in-process
\nsftp server that requires no support files when used with
\nChrootDirectory.<\/p>\n
GatewayPorts
\nSpecifies whether remote hosts are allowed to connect to ports
\nforwarded for the client.\u00a0 By default, sshd(8) binds remote
\nport forwardings to the loopback address.\u00a0 This prevents other
\nremote hosts from connecting to forwarded ports.\u00a0 GatewayPorts
\ncan be used to specify that sshd should allow remote port for\u2010
\nwardings to bind to non-loopback addresses, thus allowing other
\nhosts to connect.\u00a0 The argument may be \u201cno\u201d to force remote
\nport forwardings to be available to the local host only, \u201cyes\u201d
\nto force remote port forwardings to bind to the wildcard
\naddress, or \u201cclientspecified\u201d to allow the client to select the
\naddress to which the forwarding is bound.\u00a0 The default is \u201cno\u201d.<\/p>\n
GSSAPIAuthentication
\nSpecifies whether user authentication based on GSSAPI is
\nallowed.\u00a0 The default is \u201cno\u201d.\u00a0 Note that this option applies
\nto protocol version 2 only.<\/p>\n
GSSAPICleanupCredentials
\nSpecifies whether to automatically destroy the user’s creden\u2010
\ntials cache on logout.\u00a0 The default is \u201cyes\u201d.\u00a0 Note that this
\noption applies to protocol version 2 only.<\/p>\n
HostbasedAuthentication
\nSpecifies whether rhosts or \/etc\/hosts.equiv authentication
\ntogether with successful public key client host authentication
\nis allowed (host-based authentication).\u00a0 This option is similar
\nto RhostsRSAAuthentication and applies to protocol version 2
\nonly.\u00a0 The default is \u201cno\u201d.<\/p>\n
HostbasedUsesNameFromPacketOnly
\nSpecifies whether or not the server will attempt to perform a
\nreverse name lookup when matching the name in the ~\/.shosts,
\n~\/.rhosts, and \/etc\/hosts.equiv files during
\nHostbasedAuthentication.\u00a0 A setting of \u201cyes\u201d means that sshd(8)
\nuses the name supplied by the client rather than attempting to
\nresolve the name from the TCP connection itself.\u00a0 The default
\nis \u201cno\u201d.<\/p>\n
HostCertificate
\nSpecifies a file containing a public host certificate.\u00a0 The
\ncertificate’s public key must match a private host key already
\nspecified by HostKey.\u00a0 The default behaviour of sshd(8) is not
\nto load any certificates.<\/p>\n
HostKey
\nSpecifies a file containing a private host key used by SSH.
\nThe default is \/etc\/ssh\/ssh_host_key for protocol version 1,
\nand \/etc\/ssh\/ssh_host_dsa_key, \/etc\/ssh\/ssh_host_ecdsa_key,
\n\/etc\/ssh\/ssh_host_ed25519_key and \/etc\/ssh\/ssh_host_rsa_key for
\nprotocol version 2.\u00a0 Note that sshd(8) will refuse to use a
\nfile if it is group\/world-accessible.\u00a0 It is possible to have
\nmultiple host key files.\u00a0 \u201crsa1\u201d keys are used for version 1
\nand \u201cdsa\u201d, \u201cecdsa\u201d, \u201ced25519\u201d or \u201crsa\u201d are used for version 2
\nof the SSH protocol.\u00a0 It is also possible to specify public
\nhost key files instead.\u00a0 In this case operations on the private
\nkey will be delegated to an ssh-agent(1).<\/p>\n
HostKeyAgent
\nIdentifies the UNIX-domain socket used to communicate with an
\nagent that has access to the private host keys.\u00a0 If
\n\u201cSSH_AUTH_SOCK\u201d is specified, the location of the socket will
\nbe read from the SSH_AUTH_SOCK environment variable.<\/p>\n
IgnoreRhosts
\nSpecifies that .rhosts and .shosts files will not be used in
\nRhostsRSAAuthentication or HostbasedAuthentication.<\/p>\n
\/etc\/hosts.equiv and \/etc\/shosts.equiv are still used.\u00a0 The
\ndefault is \u201cyes\u201d.<\/p>\n
IgnoreUserKnownHosts
\nSpecifies whether sshd(8) should ignore the user’s
\n~\/.ssh\/known_hosts during RhostsRSAAuthentication or
\nHostbasedAuthentication.\u00a0 The default is \u201cno\u201d.<\/p>\n
IPQoS\u00a0\u00a0 Specifies the IPv4 type-of-service or DSCP class for the con\u2010
\nnection.\u00a0 Accepted values are \u201caf11\u201d, \u201caf12\u201d, \u201caf13\u201d, \u201caf21\u201d,
\n\u201caf22\u201d, \u201caf23\u201d, \u201caf31\u201d, \u201caf32\u201d, \u201caf33\u201d, \u201caf41\u201d, \u201caf42\u201d, \u201caf43\u201d,
\n\u201ccs0\u201d, \u201ccs1\u201d, \u201ccs2\u201d, \u201ccs3\u201d, \u201ccs4\u201d, \u201ccs5\u201d, \u201ccs6\u201d, \u201ccs7\u201d, \u201cef\u201d,
\n\u201clowdelay\u201d, \u201cthroughput\u201d, \u201creliability\u201d, or a numeric value.
\nThis option may take one or two arguments, separated by white\u2010
\nspace.\u00a0 If one argument is specified, it is used as the packet
\nclass unconditionally.\u00a0 If two values are specified, the first
\nis automatically selected for interactive sessions and the sec\u2010
\nond for non-interactive sessions.\u00a0 The default is \u201clowdelay\u201d
\nfor interactive sessions and \u201cthroughput\u201d for non-interactive
\nsessions.<\/p>\n
KbdInteractiveAuthentication
\nSpecifies whether to allow keyboard-interactive authentication.
\nThe argument to this keyword must be \u201cyes\u201d or \u201cno\u201d.\u00a0 The
\ndefault is to use whatever value
\nChallengeResponseAuthentication is set to (by default \u201cyes\u201d).<\/p>\n
KerberosAuthentication
\nSpecifies whether the password provided by the user for
\nPasswordAuthentication will be validated through the Kerberos
\nKDC.\u00a0 To use this option, the server needs a Kerberos servtab
\nwhich allows the verification of the KDC’s identity.\u00a0 The
\ndefault is \u201cno\u201d.<\/p>\n
KerberosGetAFSToken
\nIf AFS is active and the user has a Kerberos 5 TGT, attempt to
\nacquire an AFS token before accessing the user’s home direc\u2010
\ntory.\u00a0 The default is \u201cno\u201d.<\/p>\n
KerberosOrLocalPasswd
\nIf password authentication through Kerberos fails then the
\npassword will be validated via any additional local mechanism
\nsuch as \/etc\/passwd.\u00a0 The default is \u201cyes\u201d.<\/p>\n
KerberosTicketCleanup
\nSpecifies whether to automatically destroy the user’s ticket
\ncache file on logout.\u00a0 The default is \u201cyes\u201d.<\/p>\n
KexAlgorithms
\nSpecifies the available KEX (Key Exchange) algorithms.\u00a0 Multi\u2010
\nple algorithms must be comma-separated.\u00a0 The supported algo\u2010
\nrithms are:<\/p>\n
curve25519-sha256@libssh.org
\ndiffie-hellman-group1-sha1
\ndiffie-hellman-group14-sha1
\ndiffie-hellman-group-exchange-sha1
\ndiffie-hellman-group-exchange-sha256
\necdh-sha2-nistp256
\necdh-sha2-nistp384
\necdh-sha2-nistp521<\/p>\n
The default is:<\/p>\n
curve25519-sha256@libssh.org,
\necdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,
\ndiffie-hellman-group-exchange-sha256,
\ndiffie-hellman-group14-sha1<\/p>\n
KeyRegenerationInterval
\nIn protocol version 1, the ephemeral server key is automati\u2010
\ncally regenerated after this many seconds (if it has been
\nused).\u00a0 The purpose of regeneration is to prevent decrypting
\ncaptured sessions by later breaking into the machine and steal\u2010
\ning the keys.\u00a0 The key is never stored anywhere.\u00a0 If the value
\nis 0, the key is never regenerated.\u00a0 The default is 3600 (sec\u2010
\nonds).<\/p>\n
ListenAddress
\nSpecifies the local addresses sshd(8) should listen on.\u00a0 The
\nfollowing forms may be used:<\/p>\n
ListenAddress host|IPv4_addr|IPv6_addr
\nListenAddress host|IPv4_addr:port
\nListenAddress [host|IPv6_addr]:port<\/p>\n
If port is not specified, sshd will listen on the address and
\nall prior Port options specified.\u00a0 The default is to listen on
\nall local addresses.\u00a0 Multiple ListenAddress options are per\u2010
\nmitted.\u00a0 Additionally, any Port options must precede this
\noption for non-port qualified addresses.<\/p>\n
LoginGraceTime
\nThe server disconnects after this time if the user has not suc\u2010
\ncessfully logged in.\u00a0 If the value is 0, there is no time
\nlimit.\u00a0 The default is 120 seconds.<\/p>\n
LogLevel
\nGives the verbosity level that is used when logging messages
\nfrom sshd(8).\u00a0 The possible values are: QUIET, FATAL, ERROR,
\nINFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3.\u00a0 The default
\nis INFO.\u00a0 DEBUG and DEBUG1 are equivalent.\u00a0 DEBUG2 and DEBUG3
\neach specify higher levels of debugging output.\u00a0 Logging with a
\nDEBUG level violates the privacy of users and is not recom\u2010
\nmended.<\/p>\n
MACs\u00a0\u00a0\u00a0 Specifies the available MAC (message authentication code) algo\u2010
\nrithms.\u00a0 The MAC algorithm is used in protocol version 2 for
\ndata integrity protection.\u00a0 Multiple algorithms must be comma-
\nseparated.\u00a0 The algorithms that contain \u201c-etm\u201d calculate the
\nMAC after encryption (encrypt-then-mac).\u00a0 These are considered
\nsafer and their use recommended.\u00a0 The supported MACs are:<\/p>\n
hmac-md5
\nhmac-md5-96
\nhmac-ripemd160
\nhmac-sha1
\nhmac-sha1-96
\nhmac-sha2-256
\nhmac-sha2-512
\numac-64@openssh.com
\numac-128@openssh.com
\nhmac-md5-etm@openssh.com
\nhmac-md5-96-etm@openssh.com
\nhmac-ripemd160-etm@openssh.com
\nhmac-sha1-etm@openssh.com
\nhmac-sha1-96-etm@openssh.com
\nhmac-sha2-256-etm@openssh.com
\nhmac-sha2-512-etm@openssh.com
\numac-64-etm@openssh.com
\numac-128-etm@openssh.com<\/p>\n
The default is:<\/p>\n
umac-64-etm@openssh.com,umac-128-etm@openssh.com,
\nhmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,
\numac-64@openssh.com,umac-128@openssh.com,
\nhmac-sha2-256,hmac-sha2-512<\/p>\n
Match\u00a0\u00a0 Introduces a conditional block.\u00a0 If all of the criteria on the
\nMatch line are satisfied, the keywords on the following lines
\noverride those set in the global section of the config file,
\nuntil either another Match line or the end of the file.\u00a0 If a
\nkeyword appears in multiple Match blocks that are satisified,
\nonly the first instance of the keyword is applied.<\/p>\n
The arguments to Match are one or more criteria-pattern pairs
\nor the single token All which matches all criteria.\u00a0 The avail\u2010
\nable criteria are User, Group, Host, LocalAddress, LocalPort,
\nand Address.\u00a0 The match patterns may consist of single entries
\nor comma-separated lists and may use the wildcard and negation
\noperators described in the PATTERNS section of ssh_config(5).<\/p>\n
The patterns in an Address criteria may additionally contain
\naddresses to match in CIDR address\/masklen format, e.g.
\n\u201c192.0.2.0\/24\u201d or \u201c3ffe:ffff::\/32\u201d.\u00a0 Note that the mask length
\nprovided must be consistent with the address – it is an error
\nto specify a mask length that is too long for the address or
\none with bits set in this host portion of the address.\u00a0 For
\nexample, \u201c192.0.2.0\/33\u201d and \u201c192.0.2.0\/8\u201d respectively.<\/p>\n
Only a subset of keywords may be used on the lines following a
\nMatch keyword.\u00a0 Available keywords are AcceptEnv,
\nAllowAgentForwarding, AllowGroups, AllowTcpForwarding,
\nAllowUsers, AuthenticationMethods, AuthorizedKeysCommand,
\nAuthorizedKeysCommandUser, AuthorizedKeysFile,
\nAuthorizedPrincipalsFile, Banner, ChrootDirectory, DenyGroups,
\nDenyUsers, ForceCommand, GatewayPorts, GSSAPIAuthentication,
\nHostbasedAuthentication, HostbasedUsesNameFromPacketOnly,
\nKbdInteractiveAuthentication, KerberosAuthentication,
\nMaxAuthTries, MaxSessions, PasswordAuthentication,
\nPermitEmptyPasswords, PermitOpen, PermitRootLogin, PermitTTY,
\nPermitTunnel, PermitUserRC, PubkeyAuthentication, RekeyLimit,
\nRhostsRSAAuthentication, RSAAuthentication, X11DisplayOffset,
\nX11Forwarding and X11UseLocalHost.<\/p>\n
MaxAuthTries
\nSpecifies the maximum number of authentication attempts permit\u2010
\nted per connection.\u00a0 Once the number of failures reaches half
\nthis value, additional failures are logged.\u00a0 The default is 6.<\/p>\n
MaxSessions
\nSpecifies the maximum number of open sessions permitted per
\nnetwork connection.\u00a0 The default is 10.<\/p>\n
MaxStartups
\nSpecifies the maximum number of concurrent unauthenticated con\u2010
\nnections to the SSH daemon.\u00a0 Additional connections will be
\ndropped until authentication succeeds or the LoginGraceTime
\nexpires for a connection.\u00a0 The default is 10:30:100.<\/p>\n
Alternatively, random early drop can be enabled by specifying
\nthe three colon separated values \u201cstart:rate:full\u201d (e.g.
\n“10:30:60”).\u00a0 sshd(8) will refuse connection attempts with a
\nprobability of \u201crate\/100\u201d (30%) if there are currently \u201cstart\u201d
\n(10) unauthenticated connections.\u00a0 The probability increases
\nlinearly and all connection attempts are refused if the number
\nof unauthenticated connections reaches \u201cfull\u201d (60).<\/p>\n
PasswordAuthentication
\nSpecifies whether password authentication is allowed.\u00a0 The
\ndefault is \u201cyes\u201d.<\/p>\n
PermitEmptyPasswords
\nWhen password authentication is allowed, it specifies whether
\nthe server allows login to accounts with empty password
\nstrings.\u00a0 The default is \u201cno\u201d.<\/p>\n
PermitOpen
\nSpecifies the destinations to which TCP port forwarding is per\u2010
\nmitted.\u00a0 The forwarding specification must be one of the fol\u2010
\nlowing forms:<\/p>\n
PermitOpen host:port
\nPermitOpen IPv4_addr:port
\nPermitOpen [IPv6_addr]:port<\/p>\n
Multiple forwards may be specified by separating them with
\nwhitespace.\u00a0 An argument of \u201cany\u201d can be used to remove all
\nrestrictions and permit any forwarding requests.\u00a0 An argument
\nof \u201cnone\u201d can be used to prohibit all forwarding requests.\u00a0 By
\ndefault all port forwarding requests are permitted.<\/p>\n
PermitRootLogin
\nSpecifies whether root can log in using ssh(1).\u00a0 The argument
\nmust be \u201cyes\u201d, \u201cwithout-password\u201d, \u201cforced-commands-only\u201d, or
\n\u201cno\u201d.\u00a0 The default is \u201cyes\u201d.<\/p>\n
If this option is set to \u201cwithout-password\u201d, password authenti\u2010
\ncation is disabled for root.<\/p>\n
If this option is set to \u201cforced-commands-only\u201d, root login
\nwith public key authentication will be allowed, but only if the
\ncommand option has been specified (which may be useful for tak\u2010
\ning remote backups even if root login is normally not allowed).
\nAll other authentication methods are disabled for root.<\/p>\n
If this option is set to \u201cno\u201d, root is not allowed to log in.<\/p>\n
PermitTunnel
\nSpecifies whether tun(4) device forwarding is allowed.\u00a0 The
\nargument must be \u201cyes\u201d, \u201cpoint-to-point\u201d (layer 3), \u201cethernet\u201d
\n(layer 2), or \u201cno\u201d.\u00a0 Specifying \u201cyes\u201d permits both
\n\u201cpoint-to-point\u201d and \u201cethernet\u201d.\u00a0 The default is \u201cno\u201d.<\/p>\n
PermitTTY
\nSpecifies whether pty(4) allocation is permitted.\u00a0 The default
\nis \u201cyes\u201d.<\/p>\n
PermitUserEnvironment
\nSpecifies whether ~\/.ssh\/environment and environment= options
\nin ~\/.ssh\/authorized_keys are processed by sshd(8).\u00a0 The
\ndefault is \u201cno\u201d.\u00a0 Enabling environment processing may enable
\nusers to bypass access restrictions in some configurations
\nusing mechanisms such as LD_PRELOAD.<\/p>\n
PermitUserRC
\nSpecifies whether any ~\/.ssh\/rc file is executed.\u00a0 The default
\nis \u201cyes\u201d.<\/p>\n
PidFile
\nSpecifies the file that contains the process ID of the SSH dae\u2010
\nmon.\u00a0 The default is \/var\/run\/sshd.pid.<\/p>\n
Port\u00a0\u00a0\u00a0 Specifies the port number that sshd(8) listens on.\u00a0 The default
\nis 22.\u00a0 Multiple options of this type are permitted.\u00a0 See also
\nListenAddress.<\/p>\n
PrintLastLog
\nSpecifies whether sshd(8) should print the date and time of the
\nlast user login when a user logs in interactively.\u00a0 The default
\nis \u201cyes\u201d.<\/p>\n
PrintMotd
\nSpecifies whether sshd(8) should print \/etc\/motd when a user
\nlogs in interactively.\u00a0 (On some systems it is also printed by
\nthe shell, \/etc\/profile, or equivalent.)\u00a0 The default is \u201cyes\u201d.<\/p>\n
Protocol
\nSpecifies the protocol versions sshd(8) supports.\u00a0 The possible
\nvalues are \u20181\u2019 and \u20182\u2019.\u00a0 Multiple versions must be comma-sepa\u2010
\nrated.\u00a0 The default is \u20182\u2019.\u00a0 Note that the order of the proto\u2010
\ncol list does not indicate preference, because the client
\nselects among multiple protocol versions offered by the server.
\nSpecifying \u201c2,1\u201d is identical to \u201c1,2\u201d.<\/p>\n
PubkeyAuthentication
\nSpecifies whether public key authentication is allowed.\u00a0 The
\ndefault is \u201cyes\u201d.\u00a0 Note that this option applies to protocol
\nversion 2 only.<\/p>\n
RekeyLimit
\nSpecifies the maximum amount of data that may be transmitted
\nbefore the session key is renegotiated, optionally followed a
\nmaximum amount of time that may pass before the session key is
\nrenegotiated.\u00a0 The first argument is specified in bytes and may
\nhave a suffix of \u2018K\u2019, \u2018M\u2019, or \u2018G\u2019 to indicate Kilobytes,
\nMegabytes, or Gigabytes, respectively.\u00a0 The default is between
\n\u20181G\u2019 and \u20184G\u2019, depending on the cipher.\u00a0 The optional second
\nvalue is specified in seconds and may use any of the units doc\u2010
\numented in the TIME FORMATS section.\u00a0 The default value for
\nRekeyLimit is \u201cdefault none\u201d, which means that rekeying is per\u2010
\nformed after the cipher’s default amount of data has been sent
\nor received and no time based rekeying is done.\u00a0 This option
\napplies to protocol version 2 only.<\/p>\n
RevokedKeys
\nSpecifies revoked public keys.\u00a0 Keys listed in this file will
\nbe refused for public key authentication.\u00a0 Note that if this
\nfile is not readable, then public key authentication will be
\nrefused for all users.\u00a0 Keys may be specified as a text file,
\nlisting one public key per line, or as an OpenSSH Key Revoca\u2010
\ntion List (KRL) as generated by ssh-keygen(1).\u00a0 For more infor\u2010
\nmation on KRLs, see the KEY REVOCATION LISTS section in
\nssh-keygen(1).<\/p>\n
RhostsRSAAuthentication
\nSpecifies whether rhosts or \/etc\/hosts.equiv authentication
\ntogether with successful RSA host authentication is allowed.
\nThe default is \u201cno\u201d.\u00a0 This option applies to protocol version 1
\nonly.<\/p>\n
RSAAuthentication
\nSpecifies whether pure RSA authentication is allowed.\u00a0 The
\ndefault is \u201cyes\u201d.\u00a0 This option applies to protocol version 1
\nonly.<\/p>\n
ServerKeyBits
\nDefines the number of bits in the ephemeral protocol version 1
\nserver key.\u00a0 The minimum value is 512, and the default is 1024.<\/p>\n
StreamLocalBindMask
\nSets the octal file creation mode mask (umask) used when creat\u2010
\ning a Unix-domain socket file for local or remote port forward\u2010
\ning.\u00a0 This option is only used for port forwarding to a Unix-
\ndomain socket file.<\/p>\n
The default value is 0177, which creates a Unix-domain socket
\nfile that is readable and writable only by the owner.\u00a0 Note
\nthat not all operating systems honor the file mode on Unix-
\ndomain socket files.<\/p>\n
StreamLocalBindUnlink
\nSpecifies whether to remove an existing Unix-domain socket file
\nfor local or remote port forwarding before creating a new one.
\nIf the socket file already exists and StreamLocalBindUnlink is
\nnot enabled, sshd will be unable to forward the port to the
\nUnix-domain socket file.\u00a0 This option is only used for port
\nforwarding to a Unix-domain socket file.<\/p>\n
The argument must be \u201cyes\u201d or \u201cno\u201d.\u00a0 The default is \u201cno\u201d.<\/p>\n
StrictModes
\nSpecifies whether sshd(8) should check file modes and ownership
\nof the user’s files and home directory before accepting login.
\nThis is normally desirable because novices sometimes acciden\u2010
\ntally leave their directory or files world-writable.\u00a0 The
\ndefault is \u201cyes\u201d.\u00a0 Note that this does not apply to
\nChrootDirectory, whose permissions and ownership are checked
\nunconditionally.<\/p>\n
Subsystem
\nConfigures an external subsystem (e.g. file transfer daemon).
\nArguments should be a subsystem name and a command (with
\noptional arguments) to execute upon subsystem request.<\/p>\n
The command sftp-server(8) implements the \u201csftp\u201d file transfer
\nsubsystem.<\/p>\n
Alternately the name \u201cinternal-sftp\u201d implements an in-process
\n\u201csftp\u201d server.\u00a0 This may simplify configurations using
\nChrootDirectory to force a different filesystem root on
\nclients.<\/p>\n
By default no subsystems are defined.\u00a0 Note that this option
\napplies to protocol version 2 only.<\/p>\n
SyslogFacility
\nGives the facility code that is used when logging messages from
\nsshd(8).\u00a0 The possible values are: DAEMON, USER, AUTH, LOCAL0,
\nLOCAL1, LOCAL2, LOCAL3, LOCAL4, LOCAL5, LOCAL6, LOCAL7.\u00a0 The
\ndefault is AUTH.<\/p>\n
TCPKeepAlive
\nSpecifies whether the system should send TCP keepalive messages
\nto the other side.\u00a0 If they are sent, death of the connection
\nor crash of one of the machines will be properly noticed.\u00a0 How\u2010
\never, this means that connections will die if the route is down
\ntemporarily, and some people find it annoying.\u00a0 On the other
\nhand, if TCP keepalives are not sent, sessions may hang indefi\u2010
\nnitely on the server, leaving \u201cghost\u201d users and consuming
\nserver resources.<\/p>\n
The default is \u201cyes\u201d (to send TCP keepalive messages), and the
\nserver will notice if the network goes down or the client host
\ncrashes.\u00a0 This avoids infinitely hanging sessions.<\/p>\n
To disable TCP keepalive messages, the value should be set to
\n\u201cno\u201d.<\/p>\n
TrustedUserCAKeys
\nSpecifies a file containing public keys of certificate authori\u2010
\nties that are trusted to sign user certificates for authentica\u2010
\ntion.\u00a0 Keys are listed one per line; empty lines and comments
\nstarting with \u2018#\u2019 are allowed.\u00a0 If a certificate is presented
\nfor authentication and has its signing CA key listed in this
\nfile, then it may be used for authentication for any user
\nlisted in the certificate’s principals list.\u00a0 Note that cer\u2010
\ntificates that lack a list of principals will not be permitted
\nfor authentication using TrustedUserCAKeys.\u00a0 For more details
\non certificates, see the CERTIFICATES section in ssh-keygen(1).<\/p>\n
UseDNS\u00a0 Specifies whether sshd(8) should look up the remote host name
\nand check that the resolved host name for the remote IP address
\nmaps back to the very same IP address.\u00a0 The default is \u201cyes\u201d.<\/p>\n
UseLogin
\nSpecifies whether login(1) is used for interactive login ses\u2010
\nsions.\u00a0 The default is \u201cno\u201d.\u00a0 Note that login(1) is never used
\nfor remote command execution.\u00a0 Note also, that if this is
\nenabled, X11Forwarding will be disabled because login(1) does
\nnot know how to handle xauth(1) cookies.\u00a0 If
\nUsePrivilegeSeparation is specified, it will be disabled after
\nauthentication.<\/p>\n
UsePAM\u00a0 Enables the Pluggable Authentication Module interface.\u00a0 If set
\nto \u201cyes\u201d this will enable PAM authentication using
\nChallengeResponseAuthentication and PasswordAuthentication in
\naddition to PAM account and session module processing for all
\nauthentication types.<\/p>\n
Because PAM challenge-response authentication usually serves an
\nequivalent role to password authentication, you should disable
\neither PasswordAuthentication or
\nChallengeResponseAuthentication.<\/p>\n
If UsePAM is enabled, you will not be able to run sshd(8) as a
\nnon-root user.\u00a0 The default is \u201cno\u201d.<\/p>\n
UsePrivilegeSeparation
\nSpecifies whether sshd(8) separates privileges by creating an
\nunprivileged child process to deal with incoming network traf\u2010
\nfic.\u00a0 After successful authentication, another process will be
\ncreated that has the privilege of the authenticated user.\u00a0 The
\ngoal of privilege separation is to prevent privilege escalation
\nby containing any corruption within the unprivileged processes.
\nThe default is \u201cyes\u201d.\u00a0 If UsePrivilegeSeparation is set to
\n\u201csandbox\u201d then the pre-authentication unprivileged process is
\nsubject to additional restrictions.<\/p>\n
VersionAddendum
\nOptionally specifies additional text to append to the SSH pro\u2010
\ntocol banner sent by the server upon connection.\u00a0 The default
\nis \u201cnone\u201d.<\/p>\n
X11DisplayOffset
\nSpecifies the first display number available for sshd(8)’s X11
\nforwarding.\u00a0 This prevents sshd from interfering with real X11
\nservers.\u00a0 The default is 10.<\/p>\n
X11Forwarding
\nSpecifies whether X11 forwarding is permitted.\u00a0 The argument
\nmust be \u201cyes\u201d or \u201cno\u201d.\u00a0 The default is \u201cno\u201d.<\/p>\n
When X11 forwarding is enabled, there may be additional expo\u2010
\nsure to the server and to client displays if the sshd(8) proxy
\ndisplay is configured to listen on the wildcard address (see
\nX11UseLocalhost below), though this is not the default.\u00a0 Addi\u2010
\ntionally, the authentication spoofing and authentication data
\nverification and substitution occur on the client side.\u00a0 The
\nsecurity risk of using X11 forwarding is that the client’s X11
\ndisplay server may be exposed to attack when the SSH client
\nrequests forwarding (see the warnings for ForwardX11 in
\nssh_config(5)).\u00a0 A system administrator may have a stance in
\nwhich they want to protect clients that may expose themselves
\nto attack by unwittingly requesting X11 forwarding, which can
\nwarrant a \u201cno\u201d setting.<\/p>\n
Note that disabling X11 forwarding does not prevent users from
\nforwarding X11 traffic, as users can always install their own
\nforwarders.\u00a0 X11 forwarding is automatically disabled if
\nUseLogin is enabled.<\/p>\n
X11UseLocalhost
\nSpecifies whether sshd(8) should bind the X11 forwarding server
\nto the loopback address or to the wildcard address.\u00a0 By
\ndefault, sshd binds the forwarding server to the loopback
\naddress and sets the hostname part of the DISPLAY environment
\nvariable to \u201clocalhost\u201d.\u00a0 This prevents remote hosts from con\u2010
\nnecting to the proxy display.\u00a0 However, some older X11 clients
\nmay not function with this configuration.\u00a0 X11UseLocalhost may
\nbe set to \u201cno\u201d to specify that the forwarding server should be
\nbound to the wildcard address.\u00a0 The argument must be \u201cyes\u201d or
\n\u201cno\u201d.\u00a0 The default is \u201cyes\u201d.<\/p>\n
XAuthLocation
\nSpecifies the full pathname of the xauth(1) program.\u00a0 The
\ndefault is \/usr\/X11R6\/bin\/xauth.<\/p>\n
TIME FORMATS<\/p>\n
sshd(8) command-line arguments and configuration file options that
\nspecify time may be expressed using a sequence of the form:
\ntime[qualifier], where time is a positive integer value and qualifier
\nis one of the following:<\/p>\n
\u27e8none\u27e9\u00a0 seconds
\ns | S\u00a0\u00a0 seconds
\nm | M\u00a0\u00a0 minutes
\nh | H\u00a0\u00a0 hours
\nd | D\u00a0\u00a0 days
\nw | W\u00a0\u00a0 weeks<\/p>\n
Each member of the sequence is added together to calculate the total
\ntime value.<\/p>\n
Time format examples:<\/p>\n
600\u00a0\u00a0\u00a0\u00a0 600 seconds (10 minutes)
\n10m\u00a0\u00a0\u00a0\u00a0 10 minutes
\n1h30m\u00a0\u00a0 1 hour 30 minutes (90 minutes)<\/p>\n
FILES<\/p>\n
\/etc\/ssh\/sshd_config
\nContains configuration data for sshd(8).\u00a0 This file should be
\nwritable by root only, but it is recommended (though not neces\u2010
\nsary) that it be world-readable.<\/p>\n
SEE ALSO<\/p>\n
sshd(8)<\/p>\n
AUTHORS<\/p>\n
OpenSSH is a derivative of the original and free ssh 1.2.12 release by
\nTatu Ylonen.\u00a0 Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
\nTheo de Raadt and Dug Song removed many bugs, re-added newer features
\nand created OpenSSH.\u00a0 Markus Friedl contributed the support for SSH
\nprotocol versions 1.5 and 2.0.\u00a0 Niels Provos and Markus Friedl
\ncontributed support for privilege separation.<\/p>\n
COLOPHON<\/p>\n
This page is part of the openssh (Portable OpenSSH) project.\u00a0 Informa\u2010
\ntion about the project can be found at
\nhttp:\/\/www.openssh.com\/portable.html.\u00a0 If you have a bug report for
\nthis manual page, see http:\/\/www.openssh.com\/report.html.\u00a0 This page
\nwas obtained from the tarball openssh-6.7p1.tar.gz fetched from
\nhttp:\/\/ftp.eu.openbsd.org\/pub\/OpenBSD\/OpenSSH\/portable\/ on 2014-12-30.
\nIf you discover any rendering problems in this HTML version of the
\npage, or you believe there is a better or more up-to-date source for
\nthe page, or you have corrections or improvements to the information in
\nthis COLOPHON (which is not part of the original manual page), send a
\nmail to\u00a0man-pages@man7.org<\/p>\n
BSD\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 December 31, 2014\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 BSD<\/p>\n","protected":false},"excerpt":{"rendered":"
SSHD_CONFIG(5)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 BSD File Formats Manual\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SSHD_CONFIG(5) NAME sshd_config \u2014 OpenSSH SSH daemon configuration file SYNOPSIS \/etc\/ssh\/sshd_config DESCRIPTION sshd(8) reads configuration data from \/etc\/ssh\/sshd_config (or the file specified with -f on the command line).\u00a0 The file contains keyword- argument pairs, one per line.\u00a0 Lines starting with \u2018#\u2019 and empty lines are interpreted as comments.\u00a0 Arguments may […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_sitemap_exclude":false,"_sitemap_priority":"","_sitemap_frequency":"","footnotes":""},"categories":[8],"tags":[],"class_list":["post-355","post","type-post","status-publish","format-standard","hentry","category-shell"],"a3_pvc":{"activated":false,"total_views":0,"today_views":0},"_links":{"self":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/355","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=355"}],"version-history":[{"count":0,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=\/wp\/v2\/posts\/355\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=355"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=355"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.linuxboxen.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=355"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}