This repository was archived by the owner on Dec 21, 2021. It is now read-only.
Restrict permissions of private key file #235
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
siegfriedweber
force-pushed
the
restrict_file_permissions
branch
from
ac8b672 to
0b47bac
Compare
This was referenced Jul 26, 2021
The access rights of the private key file are restricted to the owner when it is created. On existing installations this must be done manually.
siegfriedweber
force-pushed
the
restrict_file_permissions
branch
from
0b47bac to
6f0c287
Compare
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.
Fixes #215
Description
The access rights of the private key file are restricted to the owner when it is created. On existing installations this must be done manually.
The fix was actually done in krustlet:
This is not testable in the agent-integration-tests.
Review Checklist