Skip to content
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

Android APK D2D: Extend and refine code matching to PurlDB #1395

Open
Tracked by #1396
pombredanne opened this issue Sep 28, 2024 · 0 comments
Open
Tracked by #1396

Android APK D2D: Extend and refine code matching to PurlDB #1395

pombredanne opened this issue Sep 28, 2024 · 0 comments

Comments

@pombredanne
Copy link
Contributor

This is a follow up to #1371

We already use directory matching to account for the specific of Android.

From recent Android project experience, my understanding of JADX is that (1) it will produce a set of .class files and a set of .source files neither of which will be a fingerprint match to the original Java code and (2) the decompiled source will be more divergent from the original source than the binaries. So wouldn't fuzzy matching for the .class files be the most important first step?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant