From: Harald Seiler <hws@denx.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] sshd-regen-keys: Fix sshd deadlock on boot
Date: Thu, 13 Dec 2018 10:48:04 +0100 [thread overview]
Message-ID: <1544694484.2560.15.camel@denx.de> (raw)
In-Reply-To: <bbc017ba-1db7-9925-9b48-d40ba07deaaf@siemens.com>
Hello Claudius,
On Thu, 2018-12-13 at 10:41 +0100, Claudius Heine wrote:
> Hi Harald,
>
> On 13/12/2018 09.56, Harald Seiler wrote:
> > Currently, when sshd-regen-keys runs dpkg-reconfigure, this
> > will lead to a call to `systemctl restart ssh`. This call blocks
> > forever because of course the sshd-regen-keys unit, which is a
> > dependency of sshd, hasn't finished at this point and can't do so
> > because it is waiting as well.
> >
> > To circumvent this deadlock, this commit changes sshd-regen-keys'
> > behavior so sshd is first disabled and only reenabled after the
> > job is done.
> >
> > Signed-off-by: Harald Seiler <hws@denx.de>
> > ---
> > .../sshd-regen-keys/files/sshd-regen-keys.service | 2 +-
> > .../sshd-regen-keys/files/sshd-regen-keys.sh | 19 +++++++++++++++++++
> > .../sshd-regen-keys/sshd-regen-keys_0.1.bb | 7 +++++--
> > 3 files changed, 25 insertions(+), 3 deletions(-)
> > create mode 100644 meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh
> >
> > diff --git a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
> > index 3b8231f..a05e1a9 100644
> > --- a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
> > +++ b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
> > @@ -10,7 +10,7 @@ ConditionPathIsReadWrite=/etc
> > Type=oneshot
> > RemainAfterExit=yes
> > Environment=DEBIAN_FRONTEND=noninteractive
> > -ExecStart=/bin/sh -c "rm -v /etc/ssh/ssh_host_*_key*; dpkg-reconfigure openssh-server"
> > +ExecStart=/usr/sbin/sshd-regen-keys.sh
> > ExecStartPost=-/bin/systemctl disable sshd-regen-keys.service
> > StandardOutput=syslog
> > StandardError=syslog
> > 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
> > new file mode 100644
> > index 0000000..294e8fa
> > --- /dev/null
> > +++ b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.sh
> > @@ -0,0 +1,19 @@
> > +#!/usr/bin/env sh
> > +
> > +echo -n "SSH server is "
> > +if systemctl is-enabled ssh; then
> > + SSHD_ENABLED="true"
> > + systemctl disable --no-reload ssh
> > +fi
> > +
> > +echo "Removing keys ..."
> > +rm -v /etc/ssh/ssh_host_*_key*
> > +
> > +echo "Regenerating keys ..."
> > +dpkg-reconfigure openssh-server
>
> Since this is part of 'meta', does it make sense to make the package
> name+service file name configurable from the bitbake configuration or is
> that too much trouble.
>
I don't quite understand what you mean, can you please
elaborate on that?
> > +
> > +if test -n $SSHD_ENABLED; then
> > + echo "Reenabling ssh server ..."
> > + systemctl enable --no-reload ssh
> > + systemctl start --no-block ssh
>
> Should the service be stopped before? Or in other words: Does it make
> sense to differentiate between sshd enabled and started in this script?
ssh.service is guaranteed to be stopped because it requires
sshd-regen-keys.service to be done before starting.
> So apart from those minor nitpicks/questions, LGTM.
>
> Kind regards,
> Claudius
>
> > +fi
> > diff --git a/meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.1.bb b/meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.1.bb
> > index 02e9e25..6f12414 100644
> > --- a/meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.1.bb
> > +++ b/meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.1.bb
> > @@ -6,9 +6,12 @@ MAINTAINER = "isar-users <isar-users@googlegroups.com>"
> > DEBIAN_DEPENDS = "openssh-server, systemd"
> >
> > SRC_URI = "file://postinst \
> > - file://sshd-regen-keys.service"
> > + file://sshd-regen-keys.service \
> > + file://sshd-regen-keys.sh"
> >
> > +do_install[cleandirs] = "${D}/lib/systemd/system \
> > + ${D}/usr/sbin"
> > do_install() {
> > - install -v -d -m 755 "${D}/lib/systemd/system"
> > install -v -m 644 "${WORKDIR}/sshd-regen-keys.service" "${D}/lib/systemd/system/sshd-regen-keys.service"
> > + install -v -m 755 "${WORKDIR}/sshd-regen-keys.sh" "${D}/usr/sbin/sshd-regen-keys.sh"
> > }
> >
>
>
--
Harald
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-62 Fax: +49-8142-66989-80 Email: hws@denx.de
next prev parent reply other threads:[~2018-12-13 9:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 8:56 Harald Seiler
2018-12-13 9:41 ` Claudius Heine
2018-12-13 9:48 ` Harald Seiler [this message]
2018-12-13 10:03 ` Claudius Heine
2018-12-13 10:09 ` Jan Kiszka
2018-12-13 12:40 ` Henning Schild
2018-12-13 12:46 ` Henning Schild
2018-12-13 13:00 ` Harald Seiler
2018-12-13 13:18 ` Henning Schild
2018-12-19 11:43 ` [PATCH v2] " Harald Seiler
2018-12-19 12:41 ` Henning Schild
2018-12-19 13:54 ` [PATCH v3] " Harald Seiler
2018-12-19 14:09 ` Henning Schild
2019-01-07 12:42 ` Maxim Yu. Osipov
2019-05-28 18:25 ` Henning Schild
2019-05-28 19:48 ` Henning Schild
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=1544694484.2560.15.camel@denx.de \
--to=hws@denx.de \
--cc=claudius.heine.ext@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