From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] dropbear: allow configuring blank password option at runtime
Date: Wed, 16 Jan 2013 15:05:09 +0000 [thread overview]
Message-ID: <15267619.7f0x1u7J0V@helios> (raw)
In-Reply-To: <92e9abc7bc28eced054b0cbd6f9eaa74eb4af670.1358347974.git.paul.eggleton@linux.intel.com>
On Wednesday 16 January 2013 14:54:17 Paul Eggleton wrote:
> Instead of using IMAGE_FEATURES to control something within a recipe,
> allow this to be set at runtime and set it during postprocessing.
> Additionally, use one postprocessing function for both openssh and
> dropbear and run it regardless of whether ssh-server-* are in
> IMAGE_FEATURES so that it still takes effect if these are installed by
> adding dropbear/openssh to IMAGE_INSTALL.
>
> Fixes [YOCTO #2578].
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> meta/classes/core-image.bbclass | 5 +-
> meta/classes/image.bbclass | 8 +-
> meta/recipes-core/dropbear/dropbear.inc | 6 +-
> .../dropbear/dropbear/allow-nopw.patch | 19 ----
> .../dropbear/dropbear/nopw-option.patch | 106
Upon further consideration, this is not going to work for anyone inheriting
from image.bbclass rather than core-image.bbclass, which is quite a lot of
people. I'll send a v2.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-01-16 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 14:54 [PATCH 0/1] dropbear: allow configuring blank password option at runtime Paul Eggleton
2013-01-16 14:54 ` [PATCH 1/1] " Paul Eggleton
2013-01-16 15:05 ` Paul Eggleton [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=15267619.7f0x1u7J0V@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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