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 19:31:05 +0200	[thread overview]
Message-ID: <20120824193105.13f01c2e@skate> (raw)
In-Reply-To: <CAAfyv37CS+Hss_-kfiv9tGZDTPpeiG-bzjyF5mqNdL61=PNupg@mail.gmail.com>

Le Fri, 24 Aug 2012 16:31:38 +0200,
Belisko Marek <marek.belisko@gmail.com> a ?crit :

> > Correct. dropbear doesn't allow login into accounts that have an
> > empty password.
> Is there any way in e.g. post-processing to set some passwd (maybe
> empty) for root user to avoid such troubles? Anybody using it that
> way?

See http://www.elinux.org/images/2/2a/Using-buildroot-real-project.pdf
slide 25. You can use the post-build script mechanism to tune
the /etc/passwd file to set a root password.

I once thought of adding a Kconfig option for that, but it would mean
that the root password would be stored as clear text in the .config
file, which probably isn't that nice.

Should we make the default 'root' password be 'root' so that it is
non-empty and it works with Dropbear? Or simply add a FAQ entry
which explains this problem? Other ideas?

Best regards,

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 17:31 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
2012-08-24 14:31     ` Belisko Marek
2012-08-24 17:31       ` Thomas Petazzoni [this message]
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=20120824193105.13f01c2e@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