Setup additional hardening for pods#168
Merged
Merged
Conversation
Signed-off-by: Pat Riehecky <riehecky@fnal.gov>
Collaborator
|
@jcpunk Thank you for this and the other related PRs over the last few weeks! Apologies I missed them in my inbox. I will release a rc version today to test and validate that includes these fixes and then tag the official candidate for you early next week. Cheers, |
Contributor
Author
|
Sounds good, I think I closed out some of the github issues, but they didn't link up? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR adds a number of security hardening best practices to the cvmfs plugins.
hostUsersseems to require the ability to chown the filesystem, which is a non-starter.The acutal mount bits all require system privileges, so they can't be locked down much further.