This website requires JavaScript.
Explore
Help
Sign In
i2p
/
i2p.i2p
Watch
1
Star
0
Fork
0
mirror of
https://github.com/i2p/i2p.i2p.git
synced
2024-12-06 19:27:00 +01:00
Code
Issues
Actions
353
Packages
Projects
Releases
Wiki
Activity
Files
32d21e5e886500a7d7bbfe01c5a477beecf1b17a
i2p.i2p
/
apps
/
jetty
T
History
zzz
cad8fe954e
Java CI / build (push)
Waiting to run
Details
Java CI / javadoc-latest (push)
Waiting to run
Details
Java CI / build-java7 (push)
Waiting to run
Details
Jetty: Don't show null exception message in XSSFilter
2024-07-02 12:00:34 -04:00
..
.externalToolBuilders
…
apache-tomcat-9.0.88
Build: Update to Tomcat 9.0.88
2024-04-17 07:45:40 -04:00
java/src/net
/i2p
Jetty: Don't show null exception message in XSSFilter
2024-07-02 12:00:34 -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
Build: Update gradle to 8.5
2024-01-28 12:09:10 +00:00
build.xml
Build: Put JspC wrapper in its own jar, used only at build time
2024-06-11 07:49:50 -04:00
README-i2p.txt
…