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

[QUESTION] End of life for security support for Jetty 9.4 #11644

Closed
smesh opened this issue Apr 10, 2024 · 5 comments
Closed

[QUESTION] End of life for security support for Jetty 9.4 #11644

smesh opened this issue Apr 10, 2024 · 5 comments

Comments

@smesh
Copy link

smesh commented Apr 10, 2024

On https://endoflife.date/eclipse-jetty security support for Jetty 9.4 looks like continuing (green Yes) without end of life for it. Probably, this information is not current and there is already end of life date for security support for Jetty 9.4?

Sorry, if github issue is not appropriate form for such questions. I will ask in another place, if somebody advise where.

@smesh smesh changed the title End of life for security support for Jetty 9.4 [QUESTION] End of life for security support for Jetty 9.4 Apr 10, 2024
@joakime
Copy link
Contributor

joakime commented Apr 10, 2024

@joakime
Copy link
Contributor

joakime commented Apr 10, 2024

Even Jetty 10 and Jetty 11 is at End of Community Support.

You should be using Jetty 12 at this point in time.
If you are still using javax.servlet you can use the ee8 environment on Jetty 12 to continue to support your old codebase.

@smesh
Copy link
Author

smesh commented Apr 11, 2024

@joakime , thank you for responding. For ee8, could I use Java 8 to compile and run?

@joakime
Copy link
Contributor

joakime commented Apr 11, 2024

@joakime , thank you for responding. For ee8, could I use Java 8 to compile and run?

That was answered in both links I sent you earlier.

Short answer, since you seem to be concerned about security updates, Java 8 is no longer supported by us, and many of our third party dependencies.

If you exclude build and test dependencies, there are about 13 dependencies (direct and transitive) that have reached end of life, and have security advisories against them, with no updates available on Java 8. We cannot update those on Jetty 9 anymore, but have updated them on Jetty 12 with its Java 17 minimum JDK requirement.

You should also know that many large companies (Google, Amazon, Microsoft, etc) have already dropped Java 8 support on their infrastructure.

At this point in time it's less maintenance hassle to upgrade to Java 11 than to stick with Java 8. As the only safe choice is to maintain ALL of your dependencies as forks and keep them up to date with manually applying security vulnerability patches on your own forks just to maintain a vulnerability free set of dependencies on Java 8.

We have already discussed internally when we will set Jetty 9 to End of Life, and the leading choice is January 2025 (and this is from the conservative voices, the others wanted Jetty 9 to be End of Life years ago)

@smesh
Copy link
Author

smesh commented Apr 12, 2024

@joakime , thank you very much for detailed and valuable explanation.

@smesh smesh closed this as completed Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants