debcrafters-packages team mailing list archive

[Nick Rosbrook <2116196@xxxxxxxxxxxxxxxxxx>]

I found the issue. I made a mistake somehow when resolving conflicts in
debian/patches/debian-config.patch.

As a result, we have `UsePAM no` at the moment, where it has
historically been `UsePAM yes` in Debian/Ubuntu.

This causes a different code path to be taken during auth. I.e., sshd
checks with shadow if the account is locked instead of going through
PAM.

** Changed in: openssh (Ubuntu)
       Status: Confirmed => In Progress

-- 
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:
  In Progress

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