label calling binary's path for SELinux #55307
Merged
Conversation
This file contains hidden or 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
capnspacehook
added
the
no-changelog
boxofrad
approved these changes
Jun 2, 2025
ryanclark
approved these changes
Jun 2, 2025
capnspacehook
force-pushed
the
capnspacehook/selinux-teleport-install-path
branch
from
3db284f to
c30cc47
Compare
Contributor
|
@capnspacehook See the table below for backport results.
|
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.
Instead of hoping the binary used to run Teleport SSH is installed in standard locations, use the path of the binary when generating the file contexts file. This will simplify SELinux configuration as SELinux will now recognize Teleport and enforce it no matter where it is in the filesystem.