From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Root password and ssh issues
Date: Fri, 7 Aug 2020 11:54:12 +0200 [thread overview]
Message-ID: <20200807115412.3b93cbc4@windsurf.home> (raw)
In-Reply-To: <12918ca7-601b-3a85-67bd-4b7953840a77@bootlin.com>
On Fri, 7 Aug 2020 11:51:02 +0200
Michael Opdenacker <michael.opdenacker@bootlin.com> wrote:
> Manuel and I have observed a strange phenomenon at least with Buildroot
> 2020.02.4...
>
> When we generate a root filesystem with Dropbear for ssh, and set the
> root password through BR2_TARGET_GENERIC_ROOT_PASSWD, we cannot manage
> to login through ssh.
>
> However, we can login as root on the console with this password, proving
> that the password was valid. If we then use the "passwd" command from
> the command line on the target to set the same password again, ssh
> access starts to work!
>
> Would you have an explanation for this behavior?
What is the state of /etc/shadow with the non-working SSH login, and
then the state of /etc/shadow after resetting the password with passwd
? I think I remember some issues with the expiration date/time of the
password, or something like that.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-07 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 9:51 [Buildroot] Root password and ssh issues Michael Opdenacker
2020-08-07 9:54 ` Thomas Petazzoni [this message]
2020-08-07 10:21 ` Michael Opdenacker
2020-08-07 11:12 ` Peter Seiderer
2020-08-07 11:16 ` Titouan Christophe
2020-08-07 11:35 ` Peter Seiderer
2020-08-07 13:41 ` Michael Opdenacker
2020-08-07 13:51 ` Peter Seiderer
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=20200807115412.3b93cbc4@windsurf.home \
--to=thomas.petazzoni@bootlin.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