public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: "IPFire: Development" <development@lists.ipfire.org>
Subject: [PATCH 3/3] ssh_config: Fix indentation mangled by Vim
Date: Sun, 28 Sep 2025 21:06:00 +0000	[thread overview]
Message-ID: <945df863-320b-45d6-9e7d-9aeacb901af4@ipfire.org> (raw)
In-Reply-To: <b38bbc6c-1cf2-4ddd-9a8e-25464475fc59@ipfire.org>

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
---
 config/ssh/ssh_config | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/config/ssh/ssh_config b/config/ssh/ssh_config
index 2fc62e116..66cb0c2cc 100644
--- a/config/ssh/ssh_config
+++ b/config/ssh/ssh_config
@@ -5,30 +5,30 @@
 
 # Set some basic hardening options for all connections
 Host *
-        # Disable undocumented roaming feature as it is known to be vulnerable
-        UseRoaming no
+	# Disable undocumented roaming feature as it is known to be vulnerable
+	UseRoaming no
 
-        # Only use secure crypto algorithms
-		KexAlgorithms mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
-        Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
-        MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128@openssh.com
+	# Only use secure crypto algorithms
+	KexAlgorithms mlkem768x25519-sha256,sntrup761x25519-sha512,sntrup761x25519-sha512@openssh.com,curve25519-sha256,curve25519-sha256@libssh.org,diffie-hellman-group-exchange-sha256
+	Ciphers aes256-gcm@openssh.com,aes128-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
+	MACs hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256,umac-128@openssh.com
 
-        # Always visualise server host keys (helps to identify key based MITM attacks)
-        VisualHostKey yes
+	# Always visualise server host keys (helps to identify key based MITM attacks)
+	VisualHostKey yes
 
-        # Use SSHFP (might work on some up-to-date networks) to look up host keys
-        VerifyHostKeyDNS yes
+	# Use SSHFP (might work on some up-to-date networks) to look up host keys
+	VerifyHostKeyDNS yes
 
-        # Send SSH-based keep alive messages to connected server to avoid broken connections
-        ServerAliveInterval 10
-        ServerAliveCountMax 30
+	# Send SSH-based keep alive messages to connected server to avoid broken connections
+	ServerAliveInterval 10
+	ServerAliveCountMax 30
 
 	# Disable TCP keep alive messages since they can be spoofed and we have SSH-based
 	# keep alive messages enabled; there is no need to do things twice here
 	TCPKeepAlive no
 
-        # Ensure only allowed authentication methods are used
-        PreferredAuthentications publickey,keyboard-interactive,password
+	# Ensure only allowed authentication methods are used
+	PreferredAuthentications publickey,keyboard-interactive,password
 
 	# Prevent information leak by hashing ~/.ssh/known_hosts
 	HashKnownHosts yes
-- 
2.51.0


      reply	other threads:[~2025-09-28 21:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-28 21:05 [PATCH 1/3] OpenSSH: Prefer AES-GCM ciphers over AES-CTR Peter Müller
2025-09-28 21:06 ` [PATCH 2/3] OpenSSH: Amend upstream default cipher changes Peter Müller
2025-09-28 21:06   ` Peter Müller [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=945df863-320b-45d6-9e7d-9aeacb901af4@ipfire.org \
    --to=peter.mueller@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