Allow encryption key files to use paths relative to a Mapfile #7181
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
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.
Currently
CONFIG MS_ENCRYPTION_KEY "/path/to/mykey.txt"only accepts an absolute path.This pull request allows this path to be relative to the Mapfile. The
msencryptcommand line application still expects a full path. When reading from aCONFIGfile a full path is also expected.Changes are similar to when the same was done for
MS_ERRORFILEin 58fd421This pull request also includes a test of decrypting a
CONNECTION- this was not previously part of msautotest.See https://mapserver.org/utilities/msencrypt.html for more details on encrypting parts of a connection object.