Scheduler used for after both SYNs have been ACKed and both sides
have closed the stream, but either we haven't ACKed their close or
they haven't ACKed ours.
Begin a kademlia style search for the key specified, which can take up to timeoutMs and
will fire the appropriate jobs on success or timeout (or if the kademlia search completes
without any match)
Begin a kademlia style search for the key specified, which can take up to timeoutMs and
will fire the appropriate jobs on success or timeout (or if the kademlia search completes
without any match)
Asynchronously send the message as requested in the message and, if the
send is successful, queue up any msg.getOnSendJob job, and register it
with the OutboundMessageRegistry (if it has a reply selector).
Asynchronously send the message as requested in the message and, if the
send is successful, queue up any msg.getOnSendJob job, and register it
with the OutboundMessageRegistry (if it has a reply selector).
Preprocess the messages from the pending list, grouping items startAt
through sendThrough (though only part of the last one may be fully
sent), delivering them through the sender/receiver.
we're (probably) searching for a LeaseSet, so to be (overly) cautious, we're sending
the request out through a tunnel w/ reply back through another tunnel.
Send a new message to the given destination, containing the specified
payload, returning true if the router feels confident that the message
was delivered.
Keep unused inbound session tags around for up to 12 minutes (2 minutes longer than
session tags are used on the outbound side so that no reasonable network lag
can cause failed decrypts)
caveat: this method isn't synchronized with the preparedKey, so don't
try to *change* the key data after already doing some
encryption/decryption (or if you do change it, be sure this object isn't
mid decrypt)
Router to receive and process this clove - the router that will open the
delivery instructions and decide what to do process it locally as an I2NPMessage,
forward it as an I2NPMessage to a router, forward it as an I2NPMessage to a Destination,
or forward it as an I2NPMessage to a tunnel.
If true, the recipient of this clove is requested to send a DeliveryStatusMessage
back via the replyThroughRouter using the getId() value for the status' message Id.
if we are serving as an introducer to them, this is the the tag that
they can publish that, when presented to us, will cause us to send
a relay introduction to the current peer
The FIPS PUB 180-2 standard specifies four secure hash algorithms (SHA-1,
SHA-256, SHA-384 and SHA-512) for computing a condensed representation of
electronic data (message).
SHA1() -
Constructor for class net.i2p.crypto.SHA1
Demo of a stripped down router - no tunnels, no netDb, no i2cp, no peer profiling,
just the SSU comm layer, crypto, and associated infrastructure, extended to handle
a new type of message ("FooMessage").
Simple CLI to splot the stat logs into per-stat files containing
#seconds since beginning and the value (ready for loading into your
favorite plotting tool)
Coordinate the management of various frequencies and rates within I2P components,
both allowing central update and retrieval, as well as distributed creation and
use.
This value indicates the stratum level of the local clock, with values
defined as follows:
Stratum Meaning
----------------------------------------------
0 unspecified or unavailable
1 primary reference (e.g., radio clock)
2-15 secondary reference (via NTP or SNTP)
16-255 reserved
The receiveStreamId will be set to this when the packet doesn't know
what ID will be assigned by the remote peer (aka this is the initial
synchronize packet)
Job that, if its allowed to, will submit the data gathered by the MessageHistory
component to some URL so that the network can be debugged more easily.