This website requires JavaScript.
Explore
Help
Sign In
i2p
/
i2p.i2p
Watch
1
Star
0
Fork
0
You've already forked i2p.i2p
mirror of
https://github.com/i2p/i2p.i2p.git
synced
2024-12-06 19:27:00 +01:00
Code
Issues
Actions
307
Packages
Projects
Releases
Wiki
Activity
Files
4b87f4d2cc0975e4e35a2dbcddaa163b03ba643c
i2p.i2p
/
apps
/
jetty
/
resources
T
History
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
..
log4j.properties
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