jrandom authored 20 years ago and zzz committed 20 years ago

integrated oOo's memory usage patch (the % shown is unfortunately % of peak, not % of max) [thanks oOo!]
cleaned up build script to make sure we always build fresh JSPs and xml [thanks oOo^2!]

jrandom authored 20 years ago and zzz committed 20 years ago

if the message has expired but hasn't exceeded the fudge factor, we still need to give it some time to be processed (we receive and validate it first, and if it reaches these jobs, we should let it continue)
logging

jrandom authored 20 years ago and zzz committed 20 years ago

new method for sanitizing content to be rendered on a web page (specifically, the routerInfo options can be hacked to contain evil html)
thanks for finding and suggesting the fix oOo!

jrandom authored 20 years ago and zzz committed 20 years ago

optional flag to allow using the standard base64 charset on decode/encode, rather than the (filename friendly) i2p charset

jrandom authored 20 years ago and zzz committed 20 years ago

be sure to fire any onFail jobs if we aren't going to pass a message off (duh)
take clock skew into account when determining whether a message is expired (duh^2)

jrandom authored 20 years ago and zzz committed 20 years ago

added basic HTTP authentication for accessing the router console (if a consolePassword is specified in the router.config)
unfortunately, this password setting is only read on router startup...

jrandom authored 20 years ago and zzz committed 20 years ago

cleaned up the validation of leaseSet/routerInfo elements being accepted so we validate only in one place (in the facade instead of both the facade and the dataStore)
don't accept entries created (too far) in the future

jrandom authored 20 years ago and zzz committed 20 years ago

another oOo catch (not sure if this is ever run - it shouldn't be, but now it'll display the silly statement more clearly :)

jrandom authored 20 years ago and zzz committed 20 years ago

this should fix the deserialization errors from tunnels.dat

jrandom authored 20 years ago and zzz committed 20 years ago

* properly describe expired leaseSets (e.g. "30s ago" instead of "in -30s")
* add a little table at the end of the netDb HTML summarizing the versions people claim to be running

jrandom authored 20 years ago and zzz committed 20 years ago

only relevent to simulations, obviously

jrandom authored 20 years ago and zzz committed 20 years ago

rather than flush any/all log messages 10 times a second, flush log messages once there are 100 of them or 10 seconds have passed, whichever comes first

jrandom authored 20 years ago and zzz committed 20 years ago

updated implementation to match the RandomSource javadocs (inclusive of both 0 and n, unlike SecureRandom, which is inclusive of 0 and exclusive of n)

jrandom authored 20 years ago and zzz committed 20 years ago

only block adding more *outbound* data, not handling data received from I2P.  The data has already been received by the router and delivered to the streaming lib (and is sitting in RAM anyway...)
logging

jrandom authored 20 years ago and zzz committed 20 years ago

have a write() timeout after 60s instead of blocking forever by default (also used when injecting data into an input stream)

jrandom authored 20 years ago and zzz committed 20 years ago

allow remote harvesting by specifying a URL to read routers from (e.g. --netDbURL http://dev.i2p.net/i2pdb/ )

jrandom authored 20 years ago and zzz committed 20 years ago

instead of the standard 'httpclient 4444' or 'httpclient 4444 squid.i2p', you can now specify a comma delimited list of outproxies:
'httpclient 4444 squid.i2p,www1.squid.i2p,www2.squid.i2p' and each individual http request goes through a randomly selected proxy
there are a few general issues with this, such as a lack of affinity (web applications that require a session to always come from a single IP address will break)
but it should work most of the time.

jrandom authored 20 years ago and zzz committed 20 years ago

disabled by default (enable through router.config 'netDb.shouldHarvest=true').
useful if you want to harvest the published router stats, since otherwise you could have data from a few hours back