From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Q. Gylstorff" <Quirin.Gylstorff@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v3] sshd-regen-keys: do not enable ssh server if previously disabled
Date: Tue, 2 Mar 2021 11:03:46 +0100 [thread overview]
Message-ID: <20210302110346.67a7b62f@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20210225074712.31768-1-Quirin.Gylstorff@siemens.com>
LGTM, i am always a fan of bumping package versions but that is often
not done. You might want to do that here, but i do not feel strong
about it.
Henning
Am Thu, 25 Feb 2021 08:47:12 +0100
schrieb "[ext] Q. Gylstorff" <Quirin.Gylstorff@siemens.com>:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
> The code 'test -n $SSHD_ENABLED' always returns "0" and enables ssh
> even if deactivated previously. Adding quotes(") to evaluate the
> variable content instead of variable name.
>
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
> Changes V2:
> - add missing space
> Changes V#:
> - clarify commit message
> meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
> a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh
> b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh index
> 910d879..50f45eb 100644 ---
> a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh +++
> b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh @@
> -12,7 +12,7 @@ rm -v /etc/ssh/ssh_host_*_key* echo "Regenerating keys
> ..." dpkg-reconfigure openssh-server
> -if test -n $SSHD_ENABLED; then
> +if [ -n "$SSHD_ENABLED" ]; then
> echo "Reenabling ssh server ..."
> systemctl enable --no-reload ssh
> fi
prev parent reply other threads:[~2021-03-02 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 7:47 Q. Gylstorff
2021-03-02 10:03 ` Henning Schild [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=20210302110346.67a7b62f@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=Quirin.Gylstorff@siemens.com \
--cc=isar-users@googlegroups.com \
/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