From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: [PATCH 2/2] ssh_config: Do not set defaults explicitly Date: Mon, 03 Feb 2020 17:44:48 +0000 Message-ID: <3CDCC8D4-A936-41CF-9044-F243B3966E70@ipfire.org> In-Reply-To: <6a71a56c-7894-adf3-23db-c8ede6bd41eb@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1688417526878675726==" List-Id: --===============1688417526878675726== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Reviewed-by: Michael Tremer > On 20 Jan 2020, at 20:05, Peter M=C3=BCller wr= ote: >=20 > Signed-off-by: Peter M=C3=BCller > --- > config/ssh/ssh_config | 27 +++++++++++++-------------- > 1 file changed, 13 insertions(+), 14 deletions(-) >=20 > diff --git a/config/ssh/ssh_config b/config/ssh/ssh_config > index 2abfae6d1..2e2ee60c3 100644 > --- a/config/ssh/ssh_config > +++ b/config/ssh/ssh_config > @@ -1,33 +1,32 @@ > -# OpenSSH client configuration > +# OpenSSH client configuration file for IPFire > # > -# set some basic hardening options for all connections > +# The full documentation is available at: https://man.openbsd.org/ssh_conf= ig > +# > + > +# Set some basic hardening options for all connections > Host * > - # disable Roaming as it is known to be vulnerable > + # Disable Roaming as it is known to be vulnerable > UseRoaming no >=20 > - # only use secure crypto algorithm > + # Only use secure crypto algorithms > KexAlgorithms curve25519-sha256(a)libssh.org,diffie-hellman-group-e= xchange-sha256 > Ciphers chacha20-poly1305(a)openssh.com,aes256-gcm(a)openssh.com,ae= s128-gcm(a)openssh.com,aes256-ctr,aes192-ctr,aes128-ctr > MACs hmac-sha2-512-etm(a)openssh.com,hmac-sha2-256-etm(a)openssh.co= m,umac-128-etm(a)openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128(a)openssh.c= om >=20 > - # always visualise server host keys (has no technical > - # effect, but helps to identify key based MITM attacks) > + # Always visualise server host keys (but helps to identify key bas= ed MITM attacks) > VisualHostKey yes >=20 > - # use SSHFP (might work on some up-to-date networks) to look up ho= st keys > + # Use SSHFP (might work on some up-to-date networks) to look up ho= st keys > VerifyHostKeyDNS yes >=20 > # send keep-alive messages to connected server to avoid broken conn= ections > ServerAliveInterval 10 > ServerAliveCountMax 6 >=20 > - # disable X11 forwarding (security risk) > - ForwardX11 no > - > - # always check server IP address > - CheckHostIP yes > - > - # ensure only allowed authentication methods are used > + # Ensure only allowed authentication methods are used > PreferredAuthentications publickey,keyboard-interactive,password >=20 > + # Prevent information leak by hashing ~/.ssh/known_hosts > + HashKnownHosts yes > + > # EOF > --=20 > 2.16.4 >=20 --===============1688417526878675726==--