This repository has been archived by the owner on Nov 8, 2021. It is now read-only.
Enhancement/centos6 support #132
Closed
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
added 2 commits
June 22, 2018 09:58
The default behavior was to drop the value into the codebase regardless of whether it was supported
|
Hi @artburkart Does this PR also includes #31 ? I have no idea about SELinux, so let's see if someone watches this and can review it... |
|
I also just noticed #97 (comment), which would mean I need to update the spec before this could go live. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I'm not sure whether there'd be any interest in adding CentOS 6 support, but this commit introduces an alternative method of enabling
AuthorizedKeysCommandwithout disabling SELinux entirely that acts as a fallback whennis_enabledis not a valid variable to set.Additionally, since you can't upgrade openssh-server to be
> 6.1on CentOS 6, these changes useAuthorizedKeysCommandRunAsrather thanAuthorizedKeysCommandUser. The way I determined whetherAuthorizedKeysCommandUserwas available bygreping thesshdbinary for the string. For some reason, I can't do the same forAuthorizedKeysCommandRunAs. I don't know where it's hiding.Let me know what you think.