Work around broken SSH login by disabling PAM for Fedora and Oracle #82
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.
What
This PR disables PAM for Fedora and Oracle.
Why
Because the build for Fedora 40 and Oracle 8 & 9 are currently broken, because PAM during SSH authentication is not working correctly in Podman. See the Jira ticket for more information.
Disabling PAM is officially not supported in Fedora & Oracle, but I couldn't find anything broken for our use-case.
For Fedora and Oracle 9 I simply created an additional config file to disable PAM, for Oracle 8 (which doesn't use
.d
-config files by default) I edited the main config.References
Jira: https://jira.greenbone.net/browse/VTA-641
Checklist
I've built the containers for Fedora 39 and 40 as well as Oracle 7, 8 and 9. They are working again / working as expected.