Invalidate .install fields containing destination filepath trying to escape their scope#6897
Merged
kit-ty-kate merged 3 commits intoocaml:masterfrom Apr 15, 2026
Merged
Conversation
…tion filepath trying to escape their scope
rjbou
approved these changes
Apr 15, 2026
…escape their scope Absolute filepaths and paths containing '..' were already forbidden by the opam manual. Per the <pkgname>.install section: > Absolute paths, or paths referencing the parent directory (..), are not allowed.
a996e3e to
ae877c0
Compare
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.
Absolute filepaths and paths containing '..' were already forbidden by the opam manual.
Per the
<pkgname>.installsection:The following dangerous pattern was previously possible:
Absolute pathname though act as if they were starting from
%{bin}%so no real issue with them.Backported to 2.5 in #6898