Document relationship of WriteSecurity and Y2Users writer #337
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.
This is part of the big modification we are doing in the separate
y2users
branch in order to ensure the interactive module of YaST2 uses theshadow
tools under the hood.We were not sure whether the UI option "Expert Options -> Password Encryption" would still work after the changes. It does work correctly and this pull request simply adds a comment explaining why.
In short, changing the option takes effect immediately and will affect all the users created after altering the value. Users created in the same YaST execution but before changing the value retain the previous encryption method. The value is finally written to the
login.defs
configuration just to make it persistent, but not to affect the current execution.