package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade: »installiertes openssh-server-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openssh (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
no more
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: openssh-server 1:8.2p1-4ubuntu0.3
ProcVersionSign
Uname: Linux 5.4.0-90-generic x86_64
ApportVersion: 2.20.11-
AptOrdering:
libpq5:amd64: Install
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckR
Date: Sat Nov 13 06:51:37 2021
ErrorMessage: »installiertes openssh-
InstallationDate: Installed on 2021-02-05 (280 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.6
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/
SourcePackage: openssh
Title: package openssh-server 1:8.2p1-4ubuntu0.3 failed to install/upgrade: »installiertes openssh-
UpgradeStatus: Upgraded to focal on 2021-04-04 (222 days ago)
Thank you for taking the time to file a bug report.
While looking at the log files that have been attached to the bug, more specifically to the DpkgTerminalLog.txt file, the following excert has caught my attention:
Nov 13 06:51:37 HP-UP17 systemd[1]: Starting OpenBSD Secure Shell server... sshd_config line 68: Directive 'ChallengeRespo nseAuthenticati on' is not allowed within a Match block
Nov 13 06:51:37 HP-UP17 sshd[19069]: /etc/ssh/
Did you perhaps modify your /etc/ssh/ sshd_config file and add a "Match" block containing a "ChallengeRespo nseAuthenticati on" directive inside it? If that is the case, then this is not supported by sshd and will prevent its initialization. If you haven't done that, please let us know and we will proceed with the investigation, probably by asking you to provide more information about your setup.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.
However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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: www.ubuntu. com/support/ community
http://