add trusted tar option to faster unpacks #284
Closed
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
orweis
reviewed
Aug 11, 2022
| tar_file_names = tar_file.getnames() | ||
| TarFileToLocalGitExtractor.validate_tar_or_throw(tar_file_names) | ||
| tar_file.extractall(path=self.local_clone_path) | ||
| if opal_common_config.TRUSTED_TAR == True: |
There was a problem hiding this comment.
I think we need a way to mark specific TARS as safe explicitly - so people won't by mistake treat unsafe tars as safe.
Kinda like React's dangerously set innerhtml
Maybe we can define a regex for the file name that can act as the identification ( and worst people can config it to ".*" for any file)
|
Not prioritized, closing |
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 is a base for discussion regarding #241 issue