Thanks for the further clarification.
We don't carry delta for openssh in Ubuntu, and since this is a low
priority bug it should really be reported against the Debian openssh
package. Could you please file a bug there and post its link here?
Thanks.
** Tags removed: server-todo
--
You
Just to add a voice to this: we see the same things migrating from 18.04
to 22.04 while controlling some embedded ARM/Debian devices running
dropbear. The key are indeed appearing in the wrong place as stated
above and the log in does not proceed as expected. We can work around
this for
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966886
Title:
ssh-copy-id and Dropbear Server
To manage notifications about this bug go to:
I found a (somehow stale) upstream PR that addresses this:
https://github.com/openssh/openssh-portable/pull/250
We could include this as an Ubuntu patch, but it would be better to
first see it merged upstream. It may be worth pinging there.
** Changed in: openssh (Ubuntu)
Status: New
I don't know much about dropbear but from your explanation it does
indeed sound like this is an upstream OpenSSH bug that should be
reported at https://bugzilla.mindrot.org/.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the problem is in this file
https://github.com/openssh/openssh-portable/blob/master/contrib/ssh-
copy-id
in line 335
dropbear*)
populate_new_ids 0
[ "$DRY_RUN" ] || printf '%s\n' "$NEW_IDS" | \
$SSH "$@" "$(installkeys_sh /etc/dropbear/authorized_keys)" \
|| exit 1
Thank you for taking the time to file a bug report.
I don't know if I fully understand the issue here. I installed dropbear
inside a container, started it, and then ran ssh-copy-id on the host in
order to copy my public key to the dropbear server. It got copied
successfully and I was able to
