[Buildroot] [Bug 16060] New: For Raspberry Pi 4, 64-bit, OpenSSH password authentication doesn't work for root
bugzilla at busybox.net
bugzilla at busybox.net
Thu May 9 22:11:49 UTC 2024
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 at buildroot.uclibc.org
Reporter: lists1 at afach.de
CC: buildroot at 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.
More information about the buildroot
mailing list