-
Notifications
You must be signed in to change notification settings - Fork 465
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
Java 17 not working #678
Comments
@h3xstream was this fixed with #672? |
Please test with the latest release : https://github.com/find-sec-bugs/find-sec-bugs/releases/tag/version-1.12.0 (New from this week) No classes found to analyze"No classes found to analyze" generally means that the target jar is not specify correctly. Command should look like: Also, make sure your target file is readable. |
@h3xstream I used the following command to scan my MD5 class from above:
as a result I got the weird error message about |
After downloading the newest release version-1.12.0. I am able to:
Problem solved 🥇 |
Thanks for the update 👌 |
Environment
FindSecBugs 1.11.0 Cli
GNU/Linux Ubuntu
Problem
Analyzing classes which were compiled with Java 17 will cause an exception:
Basically, FindSecBugs is unable to analyze classes which are compiled using Java 17.
Compiling the same code with Java 11 works well. The analysis will find the MD5 weakness.
Code
The text was updated successfully, but these errors were encountered: