From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] dropbear permission denied
Date: Mon, 27 Aug 2012 09:07:48 +0200 [thread overview]
Message-ID: <503B1CC4.2070102@relinux.de> (raw)
In-Reply-To: <3C32AECB8207924A9A228348325DB2D2905100@mntserv.meier-nt.local>
Am 27.08.2012 08:37, schrieb Dirk Lohse:
> I would prefer to set root-password "root" as default - so that dropbear works.
I would also opt for a default password.
> But would this bring up questions like "what is the default password"?
This could be mentioned in the "Welcome"-message.
Kind regards
Stephan
> Dirk
>
> -----Urspr?ngliche Nachricht-----
> Von: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com]
> Gesendet: Freitag, 24. August 2012 19:46
> An: Belisko Marek
> Cc: Dirk Lohse; buildroot at uclibc.org; buildroot at busybox.net
> Betreff: Re: [Buildroot] dropbear permission denied
>
> 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
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
next prev parent reply other threads:[~2012-08-27 7:07 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
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 [this message]
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=503B1CC4.2070102@relinux.de \
--to=sho@relinux.de \
--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