Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work around broken SSH login by disabling PAM for Fedora and Oracle #82

Merged
merged 2 commits into from
Jan 21, 2025

Conversation

n-thumann
Copy link
Member

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.

@n-thumann n-thumann force-pushed the workaround_disable_pam branch from c7dac09 to e1f0886 Compare January 20, 2025 10:12
@n-thumann n-thumann marked this pull request as ready for review January 20, 2025 10:37
@n-thumann n-thumann requested review from a team as code owners January 20, 2025 10:37
@n-thumann n-thumann enabled auto-merge (squash) January 20, 2025 10:37
@n-thumann n-thumann force-pushed the workaround_disable_pam branch from e1f0886 to 91a6792 Compare January 21, 2025 09:39
@n-thumann n-thumann merged commit 821cdbe into main Jan 21, 2025
118 of 119 checks passed
@n-thumann n-thumann deleted the workaround_disable_pam branch January 21, 2025 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants