debcrafters-packages team mailing list archive

[Nick Rosbrook <2116196@xxxxxxxxxxxxxxxxxx>]

Thanks for this. What user are you trying to connect as? Can you check
if that user has a locked password or not?

$ grep "$USER" /etc/shadow

I am not sure yet if it's a change in openssh directly, or another
package, but when I create a new questing container, I cannot ssh as the
ubuntu user after importing my key. But, once I set a password for the
ubuntu user (run `passwd ubuntu` as root), then I am able to connect via
ssh again.

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

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

** Changed in: openssh (Ubuntu)
     Assignee: (unassigned) => Nick Rosbrook (enr0n)

-- 
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