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

exit code 2 with OKAY status (v2021.12.20) #58

Open
daswars opened this issue Dec 20, 2021 · 2 comments
Open

exit code 2 with OKAY status (v2021.12.20) #58

daswars opened this issue Dec 20, 2021 · 2 comments

Comments

@daswars
Copy link

daswars commented Dec 20, 2021

Hi,

with the new update to v2021.12.20 i received a exit code 2 with a OKAY jar, why?

-- github.com/mergebase/log4j-detector v2021.12.20 (by mergebase.com) analyzing paths (could take a while).
-- Note: specify the '--verbose' flag to have every file examined printed to STDERR.
/opt/unifi-6.5.55-1d0581c00d/lib/log4j-core-2.16.0.jar contains Log4J-2.x   == 2.16.0 _OKAY_
@juliusmusseau
Copy link
Contributor

juliusmusseau commented Dec 20, 2021

Because it's best to upgrade to 2.17.0 !

I could change the exit codes for 2.15.0 to 15 and 2.16.0 to 16 - what do you think?

Or add an "--okay" option so that "2.15.0" is considered good enough and exits with a zero (but only when --okay is supplied)?

@daswars
Copy link
Author

daswars commented Dec 20, 2021

ahh cool, i think for me the "--okey" option is perfect :)
Big Thanks for the fast answer.

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

2 participants