debcrafters-packages team mailing list archive

[Marcos Alano <2116196@xxxxxxxxxxxxxxxxxx>]

I created this issue for multipass:
https://github.com/canonical/multipass/issues/4216

I don't know if there are more situations where a locked account could
be necessary, like automated deployments, etc. where it should just use
SSH.

MAybe it worth mentioning that in the release notes, maybe not.

** Bug watch added: github.com/canonical/multipass/issues #4216
   https://github.com/canonical/multipass/issues/4216

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

Title:
  Lost SSH connection with a Questing container after upgrade to OpenSSH
  10.0

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I just got a container with Questing, enabled proposed and updated
  OpenSSH.

  I cannot connect back after the upgrade because it seems the config
  for 10.0 isn't good enough for some reason.

  What I got from multipass is:
  ➜ multipass shell ubuntu2510
  shell failed: ssh failed to authenticate: 'Access denied for 'publickey'. Authentication that can continue: publickey'

  Maybe there is some change that creates an incompatibility? I'm
  worried that more people testing Questing could have problems.

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