-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[jimple2cpg] Consistent & Recursive JAR/WAR Unpacking #3078
Merged
DavidBakerEffendi
merged 9 commits into
joernio:master
from
badly-drawn-wizards:reuben/jimple2cpg/recursive-archive-unpacking
Jul 11, 2023
Merged
[jimple2cpg] Consistent & Recursive JAR/WAR Unpacking #3078
DavidBakerEffendi
merged 9 commits into
joernio:master
from
badly-drawn-wizards:reuben/jimple2cpg/recursive-archive-unpacking
Jul 11, 2023
Commits on Jul 11, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 2854777 - Browse repository at this point
Copy the full SHA 2854777View commit details -
Configuration menu - View commit details
-
Copy full SHA for 85b757c - Browse repository at this point
Copy the full SHA 85b757cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 97ec306 - Browse repository at this point
Copy the full SHA 97ec306View commit details -
Add consistent recursive jar unpacking.
Previously jimple2cpg would have two distinct code paths when importing a directory containing a jar (which would unpack the jar) compared to importing a jar directly (which would load it with soot). This change does the following - Always use the unpacking behaviour for jars - Remove jimple from the source files being processed (It can be added back if needed downstream) - Keep the .apk/.dex behaviour if imported directly (but not if contained in a directory). This maintains the existing behaviour. Some remaining work is to: - add docstrings - add unit tests for recursive unpacking - add unit tests for .apk/.dex (maybe)
Configuration menu - View commit details
-
Copy full SHA for a7185b1 - Browse repository at this point
Copy the full SHA a7185b1View commit details -
Configuration menu - View commit details
-
Copy full SHA for b7c3ca7 - Browse repository at this point
Copy the full SHA b7c3ca7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 03075f8 - Browse repository at this point
Copy the full SHA 03075f8View commit details -
Add javadocs and use copy instead of move
Since we recursively search, the class files found may include those in the original source directory, which we do not want to move. So we just copy instead.
Configuration menu - View commit details
-
Copy full SHA for 728897e - Browse repository at this point
Copy the full SHA 728897eView commit details -
Configuration menu - View commit details
-
Copy full SHA for e4a7b29 - Browse repository at this point
Copy the full SHA e4a7b29View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3482436 - Browse repository at this point
Copy the full SHA 3482436View commit details
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.