From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Root password and ssh issues
Date: Fri, 7 Aug 2020 13:12:56 +0200 [thread overview]
Message-ID: <20200807131256.5c691f3b@gmx.net> (raw)
In-Reply-To: <d0f3148a-c8d3-e5cf-68ee-030699e7abec@bootlin.com>
Hello Michael,
On Fri, 7 Aug 2020 12:21:51 +0200, Michael Opdenacker <michael.opdenacker@bootlin.com> wrote:
> Hi Thomas,
>
> Thanks for your quick reply!
>
>
> > 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.
>
>
> Here are the details
>
> # ls -la /etc/shadow
> -rw-------??? 1 1000???? 1000?????????? 190 Aug? 7? 2020 /etc/shadow
>
> # cat /etc/shadow
> root:$5$D1pz/P1l$JCZhyjzCCqmXbnPx7g/mBtNtSSKkMqgctsmV/zBmlR2:::::::
> daemon:*:::::::
> bin:*:::::::
> sys:*:::::::
> sync:*:::::::
> mail:*:::::::
> www-data:*:::::::
> operator:*:::::::
> nobody:*:::::::
>
> # passwd
> Changing password for root
> New password:
> Bad password: too short
> Retype password:
> passwd: password for root changed by root
>
> # cat /etc/shadow
> root:$1$SYGd3a37$u2RV/VOsLPqWznY4GR1jU.:13514::::::
> daemon:*:::::::
> bin:*:::::::
> sys:*:::::::
> sync:*:::::::
> mail:*:::::::
> www-data:*:::::::
> operator:*:::::::
> nobody:*:::::::
>
> # ls -la /etc/shadow
> -rw-------??? 1 1000???? 1000?????????? 174 Aug? 7? 2020 /etc/shadow
>
> I set the password the "root" (both in "menuconfig" and then through the
> "passwd" command). Only after this command can I login through ssh.
>
No problem here to login via ssh via preset password (raspberrypi4_64_defconfig with
additional dropbear enabled):
BR2_PACKAGE_DROPBEAR=y
BR2_PACKAGE_DROPBEAR_CLIENT=y
BR2_PACKAGE_DROPBEAR_DISABLE_REVERSEDNS=y
BR2_PACKAGE_DROPBEAR_SMALL=y
# BR2_PACKAGE_DROPBEAR_WTMP is not set
# BR2_PACKAGE_DROPBEAR_LASTLOG is not set
# BR2_PACKAGE_DROPBEAR_LEGACY_CRYPTO is not set
BR2_PACKAGE_DROPBEAR_LOCALOPTIONS_FILE=""
What looks strange are your /etc/shadow permissions, should give
root/root for user/group...
What is the /var/log/messages dropbear output for failure/success?
What is your config/defconfig?
Regards,
Peter
> Cheers,
>
> Michael.
>
next prev parent reply other threads:[~2020-08-07 11:12 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
2020-08-07 10:21 ` Michael Opdenacker
2020-08-07 11:12 ` Peter Seiderer [this message]
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=20200807131256.5c691f3b@gmx.net \
--to=ps.report@gmx.net \
--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