Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] dropbear permission denied
Date: Fri, 24 Aug 2012 13:53:23 +0200	[thread overview]
Message-ID: <20120824135323.654eb15b@skate> (raw)
In-Reply-To: <3C32AECB8207924A9A228348325DB2D29050F1@mntserv.meier-nt.local>

Le Fri, 24 Aug 2012 08:56:32 +0200,
"Dirk Lohse" <d.lohse@meier-nt.de> a ?crit :

> ssh/dropbear doesn't work without password (right?). I've created a
> password for root and it works. If not - maybe there is another
> problem. When target-fs is mounted read-only you should get another
> failure.

Correct. dropbear doesn't allow login into accounts that have an empty
password.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-08-24 11:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8E7CEF5A14A94EDF90F261B9ED2FC9E6@meiernt.local>
2012-08-24  6:56 ` [Buildroot] dropbear permission denied Dirk Lohse
2012-08-24 11:53   ` Thomas Petazzoni [this message]
2012-08-24 14:31     ` Belisko Marek
2012-08-24 17:31       ` Thomas Petazzoni
2012-08-27 19:52         ` Belisko Marek
     [not found]       ` <910D354268014B298DD6633E97BC1DEE@meiernt.local>
2012-08-27  6:37         ` Dirk Lohse
2012-08-27  7:07           ` Stephan Hoffmann
2012-08-28 11:06           ` Kevin Chadwick
2012-08-24 17:51 Dmitry Golubovsky
  -- strict thread matches above, loose matches on Subject: below --
2012-08-23 18:54 Belisko Marek
2012-08-24 15:06 ` Kevin Chadwick

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=20120824135323.654eb15b@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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