idk c4cfe420a6 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

..

.externalToolBuilders

…

apache-tomcat-9.0.54

Tomcat 9.0.54

2021-10-11 10:46:26 -04:00

java/src/net/i2p

…

jetty-distribution-9.3.30.v20211001

…

patches/jetty-util/src/main/java/org/eclipse/jetty/util

…

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.xml

…

README-i2p.txt

…