All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaap de Jong <jaap.dejong@nedap.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: dropbear
Date: Wed, 10 Apr 2013 16:37:33 +0200	[thread overview]
Message-ID: <5165792D.9070200@nedap.com> (raw)
In-Reply-To: <2047971.fHFQ1GD4mc@helios>

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.
I found some other way to accomplish the same though..

diff -urN a/svr-runopts.c b/svr-runopts.c
--- a/svr-runopts.c    2013-03-21 16:29:35.000000000 +0100
+++ b/svr-runopts.c    2013-04-10 15:11:51.000000000 +0200
@@ -115,7 +115,7 @@
      svr_opts.norootlogin = 0;
      svr_opts.noauthpass = 0;
      svr_opts.norootpass = 0;
-    svr_opts.allowblankpass = 0;
+    svr_opts.allowblankpass = 1;
      svr_opts.inetdmode = 0;
      svr_opts.portcount = 0;
      svr_opts.hostkey = NULL;

> Cheers,
> Paul
>



  reply	other threads:[~2013-04-10 14:54 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   ` Jaap de Jong [this message]
2013-04-10 14:47     ` dropbear Paul Eggleton
2013-04-10 14:50       ` dropbear Paul Eggleton
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=5165792D.9070200@nedap.com \
    --to=jaap.dejong@nedap.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.