From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2 2/2] use custom SSH client configuration in LFS file
Date: Mon, 10 Sep 2018 16:37:42 +0100 [thread overview]
Message-ID: <d5c7ba671f4e5f06d5b19eb5849fce243d1c7fbc.camel@ipfire.org> (raw)
In-Reply-To: <20180910142909.5725-2-peter.mueller@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Hello,
did you notice that this file is excluded from being updated on existing
installations?
How do we handle any custom changes from users here?
I merged this for new installations already.
-Michael
On Mon, 2018-09-10 at 16:29 +0200, Peter Müller wrote:
> Include OpenSSH client configuration file during build.
>
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
> lfs/openssh | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/lfs/openssh b/lfs/openssh
> index a88b2d126..0e6acc227 100644
> --- a/lfs/openssh
> +++ b/lfs/openssh
> @@ -100,5 +100,10 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
> -e 's|^#\?HostKey /etc/ssh/ssh_host_ed25519_key$$||' \
> -e 's|^#\?HostKey /etc/ssh/ssh_host_rsa_key$$|HostKey
> /etc/ssh/ssh_host_ecdsa_key\nHostKey /etc/ssh/ssh_host_ed25519_key\nHostKey
> /etc/ssh/ssh_host_rsa_key|' \
> /etc/ssh/sshd_config
> +
> + # install custom OpenSSH client configuration
> + install -v -m 644 $(DIR_SRC)/config/ssh/ssh_config \
> + /etc/ssh/ssh_config
> +
> @rm -rf $(DIR_APP)
> @$(POSTBUILD)
next prev parent reply other threads:[~2018-09-10 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 14:29 [PATCH v2 1/2] add hardened SSH client configuration Peter Müller
2018-09-10 14:29 ` [PATCH v2 2/2] use custom SSH client configuration in LFS file Peter Müller
2018-09-10 15:37 ` Michael Tremer [this message]
2018-09-10 15:48 ` Peter Müller
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=d5c7ba671f4e5f06d5b19eb5849fce243d1c7fbc.camel@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