From: Michael Tremer <michael.tremer@ipfire.org>
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 [thread overview]
Message-ID: <3CDCC8D4-A936-41CF-9044-F243B3966E70@ipfire.org> (raw)
In-Reply-To: <6a71a56c-7894-adf3-23db-c8ede6bd41eb@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2581 bytes --]
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 20 Jan 2020, at 20:05, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> config/ssh/ssh_config | 27 +++++++++++++--------------
> 1 file changed, 13 insertions(+), 14 deletions(-)
>
> 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_config
> +#
> +
> +# 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
>
> - # only use secure crypto algorithm
> + # Only use secure crypto algorithms
> KexAlgorithms curve25519-sha256(a)libssh.org,diffie-hellman-group-exchange-sha256
> Ciphers chacha20-poly1305(a)openssh.com,aes256-gcm(a)openssh.com,aes128-gcm(a)openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
> MACs hmac-sha2-512-etm(a)openssh.com,hmac-sha2-256-etm(a)openssh.com,umac-128-etm(a)openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128(a)openssh.com
>
> - # 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 based MITM attacks)
> VisualHostKey yes
>
> - # use SSHFP (might work on some up-to-date networks) to look up host keys
> + # Use SSHFP (might work on some up-to-date networks) to look up host keys
> VerifyHostKeyDNS yes
>
> # send keep-alive messages to connected server to avoid broken connections
> ServerAliveInterval 10
> ServerAliveCountMax 6
>
> - # 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
>
> + # Prevent information leak by hashing ~/.ssh/known_hosts
> + HashKnownHosts yes
> +
> # EOF
> --
> 2.16.4
>
prev parent reply other threads:[~2020-02-03 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 20:04 [PATCH 1/2] sshd_config: " Peter Müller
2020-01-20 20:05 ` [PATCH 2/2] ssh_config: " Peter Müller
2020-02-03 17:44 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CDCC8D4-A936-41CF-9044-F243B3966E70@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox