This website requires JavaScript.
Explore
Help
Sign In
marek
/
i2p.i2p
Watch
1
Star
0
Fork
0
You've already forked i2p.i2p
forked from
I2P_Developers/i2p.i2p
Code
Issues
Pull Requests
Actions
2
Packages
Projects
Releases
Wiki
Activity
Files
b607304f7be3c319b45bc76366f0b00e54be77b0
i2p.i2p
/
apps
/
jetty
History
zzz
5cbdb7d806
Tomcat 9.0.62
2022-05-02 11:31:45 -04:00
..
.externalToolBuilders
Updated Eclipse settings
2014-07-26 02:48:49 +00:00
apache-tomcat-9.0.62
Tomcat 9.0.62
2022-05-02 11:31:45 -04:00
java/src/net
/i2p
Fix package for new "filter"
2021-07-13 08:23:32 -04:00
jetty-distribution-9.3.30.v20211001
Jetty 9.3.30.v20211001
2021-10-10 12:09:12 -04:00
patches/jetty-util/src/main/java/org/eclipse/jetty
/util
Jetty 9.3.30.v20211001
2021-10-10 12:09:12 -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
reproducible builds with Gradle
2021-05-11 17:50:14 +00:00
build.xml
Jetty 9.3.30.v20211001
2021-10-10 12:09:12 -04:00
README-i2p.txt
jetty 7 first cut
2012-11-21 18:05:50 +00:00