bsc#1184131: use /etc/login.defs for shadow configuration #1152
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lslezak
reviewed
Apr 13, 2021
Co-authored-by: Ladislav Slezák <lslezak@suse.cz>
lslezak
approved these changes
Apr 13, 2021
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Back in 2019, we added support to read/write the shadow configuration from
/usr/etcand/etc(see bsc#1155735) for further details. This change was wrongly included in SLE 15 SP2 (and Leap 15.2): the shadow package included in that version only reads the settings from/etc/login.defs.This PR partially reverts those changes, so YaST will only take
/etc/login.defsinto account.CFA::ShadowConfigwithCFA::LoginDefsin theShadowConfigmoduile (used byyast2-users).CFA::ShadowConfig. It is only used in yast2-security. See bsc#1184131: use /etc/login.defs for shadow configuration yast-security#108.Fixes bsc#1184131.