Configuration to restrict SSH access #47
Merged
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
|
Should we consider having the auth keys config option be a URI instead of a path? Just so that the program isn't locked into supporting on-device only config options, and instead can just be pointed to |
I'd prefer to keep it on disk, much simpler vs. running a download on start. I imagine a common use case would be to just point it to an |
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.
A solution for:
It adds a new configuration variable,
SNIPS_SSH_AUTHORIZEDKEYSPATHto point to anauthorized_keys-like file that will restrict SSH access to the public keys defined in that file. If the envvar is not set, it will behave normally. This is opt-in and will not change default behavior.