Bug#1020235: ssh-copy-id: hangs when (root) user has no password
Package: openssh-client
Version: 1:9.0p1-1+b1
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I recently flashed my router with OpenWrt and had not (yet) defined a
password for the (root) user.
Trying to do ``ssh-copy-id root@openwrt.lan`` resulted in a hang
process. Doing ``ssh root@openwrt.lan`` worked, with I assume password
authentication.
After setting the (root) user password, ``ssh-copy-id`` asked for the
password and then successfully completed the action.
Then only way out of the hang process was sending a SIGKILL to it.
I don't know if it would act differently for a non-root user (as that's
the only user OpenWrt uses), but if it doesn't support a password-less
user, then I'd expect an error message, not a hung process.
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages openssh-client depends on:
ii adduser 3.129
ii dpkg 1.21.9
ii libc6 2.34-7
ii libedit2 3.1-20210910-1
ii libfido2-1 1.11.0-1+b1
ii libgssapi-krb5-2 1.20-1
ii libselinux1 3.4-1+b1
ii libssl3 3.0.5-2
ii passwd 1:4.11.1+dfsg1-2
ii zlib1g 1:1.2.11.dfsg-4.1
Versions of packages openssh-client recommends:
ii xauth 1:1.1.1-1
Versions of packages openssh-client suggests:
pn keychain <none>
ii ksshaskpass [ssh-askpass] 4:5.25.4-1
pn libpam-ssh <none>
pn monkeysphere <none>
ii ssh-askpass 1:1.2.4.1-15
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCYydClAAKCRDXblvOeH7b
brJCAP0YkoGNB5JzmDTh2TKYynJGnQOr4k6+NDCyslD5OCzzvgD9Etn5J1kj641m
p2Au/pxUKNeAcd83WZuVAATK6/O7sQ8=
=X5d3
-----END PGP SIGNATURE-----
Reply to: