jrandom authored 20 years ago and zzz committed 20 years ago

more zealous bc synchronization
make sure we always close the streams explicitly
logging

jrandom authored 20 years ago and zzz committed 20 years ago

more carefully retrieve a proxy
logging (w/ unique requestId)

jrandom authored 20 years ago and zzz committed 20 years ago

logging

jrandom authored 20 years ago and zzz committed 20 years ago

peers that we would crawl the entire netDb looking for (always failing, since there aren't any current
netDb entries for that peer that we would accept).
* keep a shitlist of keys we have recently searched for but were unable to find so we don't flood
* if our in-memory data store won't accept the data, its not helpful, so delete it on disk
* no need to do the preemptive refetching of a leaseSet, since we already garlic wrap it with payloads
* logging

hypercubus authored 20 years ago and zzz committed 20 years ago

NickServ capability (thanks oOo)

jrandom authored 20 years ago and zzz committed 20 years ago

handle errors initializing, and deal with logFilePatterns that don't include a full path (e.g. log-#.txt instead of logs/log-#.txt)

aum authored 20 years ago and zzz committed 20 years ago

reduced timeouts to 60secs

aum authored 20 years ago and zzz committed 20 years ago

Stasher is a Kademlia-based distributed file store (aka 'DHT')
for I2P. Written in python, it can be accessed as:
 - low level python classes, or
 - via a client socket, with simple text-based protocol, or
 - via command-line client prog (called 'stasher', unsurprisingly)

Release status is pre-alpha

Developed by aum, August 2004

aum authored 20 years ago and zzz committed 20 years ago

i2p/apps/stasher

aum authored 20 years ago and zzz committed 20 years ago

specifically created for I2P.

New Files:
 - aum.stasher - a single noderef
 - stasher - wrapper script for starting/stopping/using stasher
 - stasher.py - similar wrapper script for 'doze users
 - src/bencode.py - requisite module
 - src/i2p/stasher.py - the stasher application classes - python module

Modified Files:
 - setup.py - added code to install stasher wrapper
 - src/i2p/__init__.py - added stasher to '__all__', allowing import

jrandom authored 20 years ago and zzz committed 20 years ago

* new config property to have a tunnel start on load (default=true), so tunnels, er, start on load
* use i2ptunnel.config instead of i2ptunnel.cfg (for consistency)
* minor refactoring

jrandom authored 20 years ago and zzz committed 20 years ago

> Message-ID: <1776.202.37.75.101.1092369510.squirrel@202.37.75.101>
> From: adam@adambuckley.net
> To: jrandom@i2p.net
>
> [...]
>
> I hereby authorize my NtpClient.java and NtpMessage.java code to be
> redistributed under the BSD license for the purpose of integration with
> the I2P project, providing that I am credited as the original author of
> the code.
>
> [...]
w00t!  adam++
code migrated into core/java/src/net/i2p/time, integrated with Clock,
dropping that whole ugly pass-the-time-through-URL, and hence dropped
support for :7655/setTime.
New router.config properties to control the timestamper:
  time.sntpServerList=pool.ntp.org,pool.ntp.org,pool.ntp.org
  time.queryFrequencyMs=300000
  time.disabled=false
So, to disable, add time.disabled=true to your router.config.  It is
enabled by default.
Default router.config and startup scripts updated accordingly (since
timestamper.jar is now gone)

jrandom authored 20 years ago and zzz committed 20 years ago

stack traces (rather than "oh, we're doing it when... uh... writing to the socket")
* increase the throttle max, since we want to be able to send a few concurrent

jrandom authored 20 years ago and zzz committed 20 years ago

* detect situations where we may be inadvertantly flooding the netDb
and log them as CRIT with a stacktrace, as well as publish the count
of those events in the netDb
* detect potential netDb DoS situations by checking to see if we have
received more than 20 netDb lookups in 10 seconds, and if so,
probabalistically drop subsequent netDb messages (P=1-(10/numReceived)).
This is also published in the netDb.

jrandom authored 20 years ago and zzz committed 20 years ago

if we reach this point, bump up the expiration if necessary (otherwise the fast expire will occur with small clock skews)