Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1887928 - Latest freeipa-client update removes UsePAM from ssh configuration
Summary: Latest freeipa-client update removes UsePAM from ssh configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: freeipa
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: IPA Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException
Depends On:
Blocks: F33FinalFreezeException
TreeView+ depends on / blocked
 
Reported: 2020-10-13 15:25 UTC by Ian Collier
Modified: 2020-10-21 19:58 UTC (History)
13 users (show)

Fixed In Version: freeipa-4.8.10-6.fc34 freeipa-4.8.10-6.fc33 freeipa-4.8.10-6.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-19 18:12:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ian Collier 2020-10-13 15:25:04 UTC
Short version: freeipa-client upgraded from 4.8.9-2 to 4.8.10-5 this morning
and now no one can log in.

Longer version: the triggerin scriptlet in this package for openssh-server
contains a section called:
 # Take the values from /etc/ssh/sshd_config and put them in 04-ipa.conf

but it does not check that /etc/ssh/sshd_config.d is actually included in
the sshd_config.  Ours is not, because the configuration dates from a time
before that was a thing.  So removing those configuration entries did actually
change the config from a working one to a non-working one.  Specifically,
the "UsePAM yes" setting was removed, and now it defaults to "no".

Comment 1 Rob Crittenden 2020-10-13 15:34:00 UTC
Fixed upstream in https://pagure.io/freeipa/issue/8535

It hasn't been applied to the Fedora builds yet.

Comment 2 Fedora Update System 2020-10-13 16:05:19 UTC
FEDORA-2020-e9b167b8af has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e9b167b8af

Comment 3 Fedora Update System 2020-10-13 16:05:28 UTC
FEDORA-2020-3b90977761 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2020-10-13 16:06:13 UTC
FEDORA-2020-e142bd6b5b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e142bd6b5b

Comment 5 Fedora Update System 2020-10-13 20:18:59 UTC
FEDORA-2020-e142bd6b5b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e142bd6b5b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e142bd6b5b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2020-10-13 22:39:33 UTC
FEDORA-2020-e9b167b8af has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e9b167b8af`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e9b167b8af

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Adam Williamson 2020-10-19 16:35:22 UTC
Re-opening for F33 and proposing as an F33 Final FE. This bug can be ugly if you hit it on upgrade, it'd be good to fix it ASAP so it doesn't inconvenience people - in some circumstances it might be hard for them to access an affected system to update it to a later-published fix.

Comment 8 Geoffrey Marr 2020-10-19 17:30:27 UTC
Discussed during the 2020-10-19 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException (Final)" was made as it is a noticeable issue that cannot be fixed with an update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2020-10-19/f33-blocker-review.2020-10-19-16.01.txt

Comment 9 Fedora Update System 2020-10-19 18:12:45 UTC
FEDORA-2020-e9b167b8af has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2020-10-21 19:58:51 UTC
FEDORA-2020-e142bd6b5b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.