Changing File structure and security permissions for /etc/jsnapy#289
Merged
vnitinv merged 7 commits intoJuniper:masterfrom Jan 12, 2018
Merged
Changing File structure and security permissions for /etc/jsnapy#289vnitinv merged 7 commits intoJuniper:masterfrom
vnitinv merged 7 commits intoJuniper:masterfrom
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
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.
This pull request takes care of the file permission given to the /etc/jsnapy folder. The Permission currently given(777) are being shifted to 644. The files in /etc/jsnapy folder will be editable by only the root user only from now on.
Another Major Change that is catered in this pull request is the default path for snapshots and testfiles. These files have been moved to the user home directory.
This is how the jsnapy.cfg file looks now.