[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2023-11-15 Thread Launchpad Bug Tracker
This bug was fixed in the package openssh - 1:9.4p1-1ubuntu1

---
openssh (1:9.4p1-1ubuntu1) noble; urgency=medium

  * Merge with Debian unstable. Remaining changes:
- debian/rules: modify dh_installsystemd invocations for
  socket-activated sshd
- debian/openssh-server.postinst: handle migration of sshd_config options
  to systemd socket options on upgrade.
- debian/README.Debian: document systemd socket activation.
- debian/patches/socket-activation-documentation.patch: Document in
  sshd_config(5) that ListenAddress and Port no longer work.
- debian/openssh-server.templates: include debconf prompt explaining
  when migration cannot happen due to multiple ListenAddress values
- debian/.gitignore: drop file
- debian/openssh-server.postrm: remove systemd drop-ins for
  socket-activated sshd on purge
- debian/openssh-server.ucf-md5sum: update for Ubuntu delta
- debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move
  /run/sshd creation out of the systemd unit to a tmpfile config so
  that sshd can be run manually if necessary without having to create
  this directory by hand.
- debian/patches/systemd-socket-activation.patch: Fix sshd
  re-execution behavior when socket activation is used
- debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket
  activation functionality.
- d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no for some tests
  * Dropped changes, fixed upstream:
- d/p/fix-authorized-principals-command.patch: Fix the situation where
  sshd ignores AuthorizedPrincipalsCommand if AuthorizedKeysCommand
  is also set by checking if the value pointed to by the pointer
  'charptr' is NULL.
- debian/patches/CVE-2023-38408-1.patch: terminate process if requested
  to load a PKCS#11 provider that isn't a PKCS#11 provider in
  ssh-pkcs11.c.
- debian/patches/CVE-2023-38408-2.patch: disallow remote addition of
  FIDO/PKCS11 provider in ssh-agent.1, ssh-agent.c.
- debian/patches/CVE-2023-38408-3.patch: ensure FIDO/PKCS11 libraries
  contain expected symbols in misc.c, misc.h, ssh-pkcs11.c, ssh-sk.c.
  * Dropped changes, affected package versions not published in supported
releases:
- debian/openssh-server.postint: do not try to restart systemd units,
  and instead indicate that a reboot is required
- debian/tests/systemd-socket-activation: Reboot the testbed before 
starting the test
- debian/rules: Do not stop ssh.socket on upgrade

openssh (1:9.4p1-1) unstable; urgency=medium

  * New upstream release (https://www.openssh.com/releasenotes.html#9.4p1):
- ssh-agent(1): PKCS#11 modules must now be specified by their full
  paths. Previously dlopen(3) could search for them in system library
  directories.
- ssh(1): allow forwarding Unix Domain sockets via ssh -W.
- ssh(1): add support for configuration tags to ssh(1). This adds a
  ssh_config(5) "Tag" directive and corresponding "Match tag" predicate
  that may be used to select blocks of configuration similar to the
  pf.conf(5) keywords of the same name.
- ssh(1): add a "match localnetwork" predicate. This allows matching on
  the addresses of available network interfaces and may be used to vary
  the effective client configuration based on network location.
- ssh(1), sshd(8), ssh-keygen(1): infrastructure support for KRL
  extensions. This defines wire formats for optional KRL extensions and
  implements parsing of the new submessages. No actual extensions are
  supported at this point.
- sshd(8): AuthorizedPrincipalsCommand and AuthorizedKeysCommand now
  accept two additional %-expansion sequences: %D which expands to the
  routing domain of the connected session and %C which expands to the
  addresses and port numbers for the source and destination of the
  connection.
- ssh-keygen(1): increase the default work factor (rounds) for the
  bcrypt KDF used to derive symmetric encryption keys for passphrase
  protected key files by 50%.
- ssh-agent(1): improve isolation between loaded PKCS#11 modules by
  running separate ssh-pkcs11-helpers for each loaded provider.
- ssh(1): make -f (fork after authentication) work correctly with
  multiplexed connections, including ControlPersist (closes: #348741).
- ssh(1): make ConnectTimeout apply to multiplexing sockets and not just
  to network connections.
- ssh-agent(1), ssh(1): improve defences against invalid PKCS#11 modules
  being loaded by checking that the requested module contains the
  required symbol before loading it.
- sshd(8): fix AuthorizedPrincipalsCommand when AuthorizedKeysCommand
  appears before it in sshd_config. Since OpenSSH 8.7 the
  AuthorizedPrincipalsCommand directive was incorrectly ignored in this
  situation.
- sshd(8), ssh(1), ssh-keygen(1): 

[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-05-18 Thread Sergio Durigan Junior
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 received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-05-16 Thread Gertjan
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 production systems, but the behaviour is confusing (and
obviously not consistent between 18.04 and 22.04).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-05-09 Thread Paride Legovini
** Tags added: server-todo

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-05-09 Thread Paride Legovini
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 => Triaged

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-05-07 Thread Tobias Heider
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
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  New

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-03-31 Thread Ramin
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
ADDED=$(printf '%s\n' "$NEW_IDS" | wc -l)
;;

dropbear only uses the file /etc/dropbear/authorized_keys if it was patched 
in the upstream version of dropbear the patch is not included

im working with some embedded systems where the file
/etc/dropbear/authorized_keys is not writeable

with older ubuntu systems ssh-copy-id was working 
but since that change in ssh-copy-id can't install the ssh key anymore



** Changed in: openssh (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  New

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1966886] Re: ssh-copy-id and Dropbear Server

2022-03-30 Thread Sergio Durigan Junior
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 login via SSH without issues later.

Could you please provide reproduction steps here?  Also, from your
description, it doesn't seem like this is an openssh bug.  But first we
need to verify whether this is really an issue or not.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886

Title:
  ssh-copy-id and Dropbear Server

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  on Dropbear SSH Servers ssh-copy-id installs the key in
  /etc/dropbear/authorized_keys

  only the openwrt dropbear server uses that path
  
https://github.com/openwrt/openwrt/blob/2211ee0037764e1c6b1576fe7a0975722cd4acdc/package/network/services/dropbear/patches/100-pubkey_path.patch

  the upstream dropbear server uses the normal path
  ~/.ssh/authorized_keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1966886/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp