From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 16060] New: For Raspberry Pi 4, 64-bit, OpenSSH password authentication doesn't work for root
Date: Thu, 09 May 2024 22:11:49 +0000 [thread overview]
Message-ID: <bug-16060-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=16060
Bug ID: 16060
Summary: For Raspberry Pi 4, 64-bit, OpenSSH password
authentication doesn't work for root
Product: buildroot
Version: 2024.02.1
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: lists1@afach.de
CC: buildroot@uclibc.org
Target Milestone: ---
Hello everyone
I'm new to buildroot. I tried the 32-bit version (armv7) with that Raspberry Pi
4 machine. All went well. I used it for a while, all good.
The configuration I used is basic, starting from `make raspberrypi4_defconfig`,
the only things I changed were the root password + installed OpenSSH from the
packages in `make menuconfig`, followed by `make all`.
I realized I needed aarch64 architecture. I wiped the directory, extracted the
tar, and started over. I followed the same steps, but starting with `make
raspberrypi4_64_defconfig`, adding OpenSSH and setting the root password (same
password from before), followed by `make all`. Flashed the imaged to an sd
card, booted, all good.
Then, I tried to login with ssh, and I always got that the password is
incorrect. I confirmed multiple times that the password is correct. No use.
I'm no pro, so I don't know how to use serial port or fancy stuff like that. I
took the sd card out, mounted it, and added my ssh public key to
authiorized_keys of root. Put back the sd card, and ssh then worked fine. I
logged in.
Then, once I was in, I kept trying to login with the password, never worked.
Loopback didn't work either. I changed the password multiple times. I tried
many things, including manually putting the password in /etc/shadow, and
running `passwd`, and confirming that the password in /etc/shadow is changing,
but no use. I think it may be a bug in the build process, but I can't be sure.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-05-09 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 22:11 bugzilla [this message]
2024-05-10 11:24 ` [Buildroot] [Bug 16060] For Raspberry Pi 4, 64-bit, OpenSSH password authentication doesn't work for root bugzilla
2024-05-10 11:49 ` bugzilla
2024-06-15 15:22 ` bugzilla
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=bug-16060-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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