zzz 3502ff3de3 Jetty: Log RuntimeExceptions as error with stack trace ...

so we don't need to add a log override to get the stack trace

2026-06-18 08:25:41 -04:00

..

.externalToolBuilders

Updated Eclipse settings

2014-07-26 02:48:49 +00:00

apache-tomcat-9.0.107

Tomcat 9.0.107

2025-07-27 14:52:40 -04:00

java/src/net/i2p

Jetty: Log RuntimeExceptions as error with stack trace

2026-06-18 08:25:41 -04:00

jetty-home-12.0.28

Update to Jetty 12.0.28, add jars

2025-10-15 12:17:37 -04:00

jetty-home-12.0.32/lib

Debian: Require libjetty12-java 12.0.32-2

2026-03-13 08:35:40 -04:00

resources

disable any chance of JNDI lookups in log4j.properties file by setting %m{nolookups}. I don't think we're actually vulnerable to CVE-2021-44228 if I'm understanding correctly, by default it doesn't seem like we actually use log4j for much of anything and we don't do much logging of arbitrarily crafted remote inputs, but also it seems like this JNDI lookups thing is way more trouble than it could possibly be worth to us. Maybe it's a good idea to make sure it's turned off by default.

2021-12-10 21:01:37 -05:00

build.gradle

Build: Gradle fixes for Jetty 12

2026-03-19 19:27:22 -04:00

build.xml

Debian: Require libjetty12-java 12.0.32-2

2026-03-13 08:35:40 -04:00

README-i2p.txt

jetty 7 first cut

2012-11-21 18:05:50 +00:00