public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 2/2] backup: Add /etc/ssh/sshd_config.d
Date: Mon, 09 Dec 2024 11:32:59 +0000	[thread overview]
Message-ID: <F497E608-7337-4F27-BDF4-0319BF47A1B6@ipfire.org> (raw)
In-Reply-To: <20241207150400.2159-2-stefan.schantl@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 986 bytes --]

Thank you Stefan.

I believe that we need to merge this patch set and use it to load the legacy RSA key on systems that still have one.

We currently hard-code this into the configuration file, but then we then don’t generate the key any more on new installations.

I will send a patch for this, and this change will need to go into Core Update 190.

Best,
-Michael

> On 7 Dec 2024, at 15:04, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> config/backup/include | 1 +
> 1 file changed, 1 insertion(+)
> 
> diff --git a/config/backup/include b/config/backup/include
> index f0708c87f..0bf9440d3 100644
> --- a/config/backup/include
> +++ b/config/backup/include
> @@ -10,6 +10,7 @@ etc/logrotate.d
> etc/passwd
> etc/shadow
> etc/ssh/sshd_config
> +etc/ssh/sshd_config.d
> etc/ssh/ssh_host*
> etc/squid/squid.conf.local
> etc/squid/squid.conf.pre.local
> -- 
> 2.45.2
> 


      reply	other threads:[~2024-12-09 11:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-07 15:03 [PATCH 1/2] openssh: Introduce include directory for additional sshd config files Stefan Schantl
2024-12-07 15:04 ` [PATCH 2/2] backup: Add /etc/ssh/sshd_config.d Stefan Schantl
2024-12-09 11:32   ` 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=F497E608-7337-4F27-BDF4-0319BF47A1B6@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