From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jaap de Jong <jaap.dejong@nedap.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: dropbear
Date: Wed, 10 Apr 2013 15:50:01 +0100 [thread overview]
Message-ID: <1683367.FB5G2sIQUU@helios> (raw)
In-Reply-To: <2302654.XPc2iUTDec@helios>
On Wednesday 10 April 2013 15:47:09 Paul Eggleton wrote:
> On Wednesday 10 April 2013 16:37:33 Jaap de Jong wrote:
> > On 04/10/2013 04:04 PM, Paul Eggleton wrote:
> > > On Wednesday 10 April 2013 14:55:02 Jaap de Jong wrote:
> > >> dropbear 2013.56 is currently the most recent version.
> > >> Although not documented, they left out the functionality patched in
> > >> with
> > >> allow-nopw.patch in the 2013.56 release.
> > >
> > > How did you find this out?
> >
> > the patch fails and inspection of the code learns that it can't be
> > applied.
>
> Ah right - to explain what has happened, I developed a new patch to change
> dropbear so that the functionality is now controlled through a command-line
> switch, and that is now configured in the image using a script in
> /etc/default/; if you look at the dropbear recipe in master you can see how
> it works. This avoids the need to rebuild dropbear depending upon the value
> of IMAGE_FEATURES which was not really ideal.
>
> If you want to use the latest version of dropbear with an older branch I'd
> suggest just taking the dropbear recipe in master, removing the nopw-option
> patch (which has been applied).
If you do do this you'll also need to apply this patch:
http://cgit.openembedded.org/openembedded-core/commit/?id=0937054e6e3e02565f57e60a8bdc14b0ad62e249
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-04-10 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 12:55 dropbear Jaap de Jong
2013-04-10 14:04 ` dropbear Paul Eggleton
2013-04-10 14:37 ` dropbear Jaap de Jong
2013-04-10 14:47 ` dropbear Paul Eggleton
2013-04-10 14:50 ` Paul Eggleton [this message]
2013-04-10 15:10 ` dropbear Jaap de Jong
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=1683367.FB5G2sIQUU@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jaap.dejong@nedap.com \
--cc=openembedded-devel@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