From: Roland Hieber <rhi@pengutronix.de>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: Artur Wiebe <artur@4wiebe.de>, ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] DRAFT: openssh: make host key generation optional
Date: Sun, 15 Nov 2020 18:08:56 +0100 [thread overview]
Message-ID: <20201115170856.jks4rspmj6cf66dv@pengutronix.de> (raw)
In-Reply-To: <20201115100612.GA346376@lenoch>
On Sun, Nov 15, 2020 at 11:06:12AM +0100, Ladislav Michl wrote:
> On Sat, Nov 14, 2020 at 09:34:47PM +0100, Roland Hieber wrote:
> > On Fri, Nov 13, 2020 at 06:46:48PM +0100, Ladislav Michl wrote:
> > > On Fri, Nov 13, 2020 at 03:19:55PM +0100, Artur Wiebe wrote:
> > > > How can openssh.postinst be disabled from within the rule files?
> > >
> > > The very same could be achieved with symlink in your BSP:
> > > projectroot/etc/rc.once.d/openssh -> /dev/null
> >
> > I don't understand why you want to disable this. The SSH server will not
> > start without host keys. Or do you want to install a static version of
> > the host keys generated at build time?
>
> Yes, keys are static, generated at build time. Root filesystem is
> read-only.
>
> > If so, there should be an option for this. But for now, in my opinion,
> > disabling OPENSSH_SSHD_GENKEYS will just lead to a broken SSH server.
>
> As this is easy to solve at BSP level I never thought it could
> be a thing :)
OK, but at least I would mention it in the kconfig help text. The
openssh recipe could also just pick up /etc/ssh/ssh_host_*_key via
install_alternative if this option is disabled.
- Roland
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2020-11-15 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 14:19 Artur Wiebe
2020-11-13 17:46 ` Ladislav Michl
2020-11-14 20:34 ` Roland Hieber
2020-11-15 10:06 ` Ladislav Michl
2020-11-15 17:08 ` Roland Hieber [this message]
2020-11-16 9:36 ` Michael Olbrich
2020-11-16 9:45 ` [ptxdist] ?==?utf-8?q? ?==?utf-8?q? [PATCH] DRAFT:?==?utf-8?q? " Artur Wiebe
2020-11-16 10:32 ` [ptxdist] ?= [PATCH] DRAFT:=?utf-8?q? " Michael Olbrich
2020-11-16 15:09 ` [ptxdist] ?==?utf-8?q? ?==?utf-8?q? ?= [PATCH]?==?utf-8?q? DRAFT:l Artur Wiebe
2020-11-17 6:55 ` [ptxdist] ?= ?==?utf-8?q? " Michael Olbrich
2020-11-16 15:26 ` [ptxdist] ?= [PATCH] DRAFT:=?utf-8?q? openssh: make host key generation optional Denis Osterland-Heim
2020-11-16 19:16 ` [ptxdist] ?==?utf-8?q? ?==?utf-8?q? ?= [PATCH]?==?utf-8?q? DRAFT:l Artur Wiebe
2020-11-17 11:24 ` [ptxdist] ?= ?==?utf-8?q? " Roland Hieber
2020-11-17 11:29 ` [ptxdist] ?= " Roland Hieber
2020-11-16 9:36 ` [ptxdist] [PATCH] DRAFT: openssh: make host key generation optional Michael Olbrich
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=20201115170856.jks4rspmj6cf66dv@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=artur@4wiebe.de \
--cc=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.de \
/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