This repository was archived by the owner on Apr 15, 2020. It is now read-only.
resolve #340208 - Command injection in 'pdf-image', Severity:Medium#39
Open
roest01 wants to merge 2 commits intomooz:masterfrom
Open
resolve #340208 - Command injection in 'pdf-image', Severity:Medium#39roest01 wants to merge 2 commits intomooz:masterfrom
roest01 wants to merge 2 commits intomooz:masterfrom
Conversation
a33ba3e to
bb7fa45
Compare
Contributor
Author
|
This branch should be reviewed because the security report is going into a public disclosure soon. |
…6.1) - fix mooz#38 - solution for v2
bb7fa45 to
ec54d22
Compare
Contributor
Author
|
rebased - Jul 10 2018 |
Open
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I've published v2.0.1 with this PR because of #38 .
Tried to fix v1 from 2ab80d7 as well but it's not an easy merge because of the v2 code changes.
Where is Version 1.1.0 ?
Last commit 2ab80d7 in master shows v1.0.2 ...
May i prepare an v1.1.1 (or v1.0.3) starting e633ad5 ?
If yes can you create an release/v1 branch where i can merge my hotfix code into?
otherwise the recommendation is: update to v2.0.1 because of security issues and v1 keep unfixed.