diff --git a/i2p2www/pages/site/about/browser-config.html b/i2p2www/pages/site/about/browser-config.html index ac2056bd..e3b56988 100644 --- a/i2p2www/pages/site/about/browser-config.html +++ b/i2p2www/pages/site/about/browser-config.html @@ -91,10 +91,10 @@ that only set amount of accesses are allowed per client. Once the limit is reached, the client is blocked out for a timeframe of 1min/1h/1 day. Be respectful and do not overload these services with too many requests! {%- endtrans %}

-

{% trans -%} +

{% trans tpb=i2pconv('tpb.i2p') -%} Filtering is active on these outproxies (for example, mibbit and torrent tracker access is blocked). Note that even though the pirate bay is blocked -they host an official eepsite at tpb.i2p. Eepsites +they host an official eepsite at {{ tpb }}. Eepsites that are accessible via .i2p addresses are also not allowed via the outproxies. As a convenience, False.i2p blocks ad servers. {%- endtrans %}

diff --git a/i2p2www/pages/site/about/hall-of-fame.html b/i2p2www/pages/site/about/hall-of-fame.html index 346feb8a..833f8ff9 100644 --- a/i2p2www/pages/site/about/hall-of-fame.html +++ b/i2p2www/pages/site/about/hall-of-fame.html @@ -14,11 +14,11 @@ Current balance: as of {{ date }} {% trans euroval='100.0' %}{{ euroval }} €{% endtrans %}
{{ _('I2PHex bounty') }}: {% trans euroval='60.0' %}{{ euroval }} €{% endtrans %}
-{{ _('I2P in debian mirrors') }}: +{{ _('I2P in debian mirrors') }}: {% trans euroval='113.0' %}{{ euroval }} €{% endtrans %}
-{{ _('Bitcoin client for I2P') }}: +{{ _('Bitcoin client for I2P') }}: {% trans euroval='30.0', btcval='118.34' %}{{ euroval }} € and {{ btcval }} BTC{% endtrans %}
-{{ _('Unit Tests for I2P router') }}: +{{ _('Unit Tests for I2P router') }}: {% trans euroval='2700' %}{{ euroval }} €{% endtrans %}
{{ _('Bounty Robert') }}: 0
{{ _('Bounty Syndie') }}: 100 BTC
diff --git a/i2p2www/pages/site/about/intro.html b/i2p2www/pages/site/about/intro.html index 5c979f5b..4516f101 100644 --- a/i2p2www/pages/site/about/intro.html +++ b/i2p2www/pages/site/about/intro.html @@ -66,8 +66,8 @@ technique to run an anonymous IRC network (where the IRC server is hosted anonymously, and standard IRC clients use an I2PTunnel to contact it). There are other application development efforts going on as well, such as one to build an optimized swarming file transfer application (a la -BitTorrent), a -distributed data store (a la Freenet / +BitTorrent), a +distributed data store (a la Freenet / MNet), and a blogging system (a fully distributed LiveJournal), but those are not ready for use yet. diff --git a/i2p2www/pages/site/about/performance/history.html b/i2p2www/pages/site/about/performance/history.html index f8984dac..59f92ba9 100644 --- a/i2p2www/pages/site/about/performance/history.html +++ b/i2p2www/pages/site/about/performance/history.html @@ -9,13 +9,14 @@ for current issues and thoughts.

{{ _('Native math') }}

[{{ _('implemented') }}] -

{% trans modpow='http://java.sun.com/j2se/1.4.2/docs/api/java/math/BigInteger.html#modPow(java.math.BigInteger,%20java.math.BigInteger)', +

{% trans modpow='http://docs.oracle.com/javase/1.4.2/docs/api/java/math/BigInteger.html#modPow(java.math.BigInteger,%20java.math.BigInteger)', +gmp='http://gmplib.org/', jbigi=site_url('misc/jbigi') -%} When I last profiled the I2P code, the vast majority of time was spent within one function: java.math.BigInteger's modPow. Rather than try to tune this method, we'll call out to -GNU MP - an insanely fast math library +GNU MP - an insanely fast math library (with tuned assembler for many architectures). (Editor: see NativeBigInteger for faster public key cryptography) {%- endtrans %}

diff --git a/i2p2www/pages/site/about/team.html b/i2p2www/pages/site/about/team.html index bbdff18f..68974c6e 100644 --- a/i2p2www/pages/site/about/team.html +++ b/i2p2www/pages/site/about/team.html @@ -37,7 +37,7 @@ network. {{ _('manage the project mirrors') }} - {% trans monotone=site_url('get-involved/develop/monotone') %}Monotone guru{% endtrans %} + {% trans monotone=site_url('get-involved/guides/monotone') %}Monotone guru{% endtrans %} welterde, eche|on {{ _('manage the public monotone repositories') }} diff --git a/i2p2www/pages/site/comparison/freenet.html b/i2p2www/pages/site/comparison/freenet.html index 1597cf79..cc4c1dbe 100644 --- a/i2p2www/pages/site/comparison/freenet.html +++ b/i2p2www/pages/site/comparison/freenet.html @@ -13,7 +13,7 @@ built applications on top of it to do more generic anonymous communication, such static websites and message boards. {%- endtrans %}

-

{% trans -%} +

{% trans tahoe='https://tahoe-lafs.org/trac/tahoe-lafs' -%} Compared to I2P, Freenet offers some substantial benefits - it is a distributed data store, while I2P is not, allowing people to retrieve the content published by others even when the publisher is no longer online. In addition, it should be able to @@ -22,7 +22,7 @@ this functionality. On the other hand, there is overlap for users who simply wa communicate with each other anonymously through websites, message boards, file sharing programs, etc. There have also been some attempts to develop a distributed data store to run on top of I2P, -(most recently a port of Tahoe-LAFS) +(most recently a port of Tahoe-LAFS) but nothing is yet ready for general use. {%- endtrans %}

diff --git a/i2p2www/pages/site/comparison/other-networks.html b/i2p2www/pages/site/comparison/other-networks.html index a8040c4e..61373ac3 100644 --- a/i2p2www/pages/site/comparison/other-networks.html +++ b/i2p2www/pages/site/comparison/other-networks.html @@ -23,8 +23,8 @@ You may contribute an analysis by entering a

Morphmix / Tarzan

-[Morphmix] - [Tarzan] +[Morphmix] + [Tarzan]

{% trans threatmodel=site_url('docs/how/threat-model') -%} Morphmix and Tarzan are both fully distributed, peer to peer networks of @@ -174,7 +174,7 @@ both Mixminion and Mixmaster take the directory based approach as well.

JAP

[JAP] -

{% trans -%} +

{% trans url='https://www.datenschutzzentrum.de/material/themen/presse/anonip3_e.htm' -%} JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing web requests, and as such it has a few centralized nodes (participants in the cascade) that blend and mix requests from clients through the sequence of nodes (the cascade) before @@ -184,7 +184,7 @@ are not satisfied with an Anonymizer-like service, JAP is worth reviewing. One caution to note is that anyone under the jurisdiction of the German courts may want to take care, as the German Federal Bureau of Criminal Investigation (FBCI) has successfully mounted an -attack +attack on the network. Even though the method of this attack was later found to be illegal in the German courts, the fact that the data was successfully collected is the concern. Courts change their minds based upon circumstance, and this is evidence that @@ -194,11 +194,11 @@ if it may be found inadmissible in some courts later)

MUTE / AntsP2P

[MUTE] - [AntsP2P] + [AntsP2P] -

{% trans -%} +

{% trans antnet='http://citeseer.ist.psu.edu/57701.html' -%} Both of these systems work through the same basic -antnet routing, providing some degree of +antnet routing, providing some degree of anonymity based on the threat model of providing plausible deniability against a simple non-colluding adversary. With the antnet routing, they first either do a random walk or a broadcast search to find some peer with the data or identity desired, and then use a feedback diff --git a/i2p2www/pages/site/contact.html b/i2p2www/pages/site/contact.html index c10ee671..e8c5502f 100644 --- a/i2p2www/pages/site/contact.html +++ b/i2p2www/pages/site/contact.html @@ -4,7 +4,7 @@

IRC

{% trans -%} Our primary IRC network is the Irc2P network within I2P; a default tunnel to this network is set up with new router installs. - We are also present on multiple standard networks like OFTC, + We are also present on multiple standard networks like OFTC, EIN and Freenode. All I2P-related channels on all these network are linked to the main channels on Irc2P via relay bots. {%- endtrans %}

diff --git a/i2p2www/pages/site/docs/api/i2pcontrol.html b/i2p2www/pages/site/docs/api/i2pcontrol.html index c5052edf..d3f50466 100644 --- a/i2p2www/pages/site/docs/api/i2pcontrol.html +++ b/i2p2www/pages/site/docs/api/i2pcontrol.html @@ -57,7 +57,7 @@ Parameters are only provided in a named way (maps).
    GetRate – {% trans %}Fetches rateStat from router statManager. Creates stat if not already created.{% endtrans %}
      {{ _('Request:') }} -
    • Stat – [String] {% trans %}Determines which rateStat to fetch, see ratestats.{% endtrans %}
      • +
    • Stat – [String] {% trans ratestats=site_url('misc/ratestats') %}Determines which rateStat to fetch, see ratestats.{% endtrans %}
    • Period – [long] {% trans %}Determines which period a stat is fetched for. Measured in ms.{% endtrans %}
    • Token – [String] {% trans %}Token used for authenticating the client. Is provided by the server via the 'Authenticate' RPC method.{% endtrans %}
    diff --git a/i2p2www/pages/site/docs/api/sam.html b/i2p2www/pages/site/docs/api/sam.html index 2f789bd1..3297fe63 100644 --- a/i2p2www/pages/site/docs/api/sam.html +++ b/i2p2www/pages/site/docs/api/sam.html @@ -34,9 +34,9 @@ the key=value pairs can change (e.g. "ONE TWO A=B C=D" or addition, the protocol is case-sensitive. Communication can take three distinct forms: -* Virtual streams -* Repliable datagrams (messages with a FROM field) -* Anonymous datagrams (raw anonymous messages) +* Virtual streams +* Repliable datagrams (messages with a FROM field) +* Anonymous datagrams (raw anonymous messages) ---------------------------------------------------------------------- SAM connection handshake @@ -334,8 +334,8 @@ Tunnel, I2CP, and Streaming Options These options may be passed in as name=value pairs at the end of a SAM SESSION CREATE line. -All sessions may include I2CP options such as tunnel lengths. -STREAM sessions may include Streaming lib options. +All sessions may include I2CP options such as tunnel lengths. +STREAM sessions may include Streaming lib options. See those references for option names and defaults. @@ -351,7 +351,7 @@ Client library implementations: ---------------------------------------------------------------------- Client libraries are available for C, C++, C#, Perl, and Python. -These are in the apps/sam/ directory in the I2P Source Package. +These are in the apps/sam/ directory in the I2P Source Package. ---------------------------------------------------------------------- diff --git a/i2p2www/pages/site/docs/api/samv2.html b/i2p2www/pages/site/docs/api/samv2.html index 296d0cba..b4707c90 100644 --- a/i2p2www/pages/site/docs/api/samv2.html +++ b/i2p2www/pages/site/docs/api/samv2.html @@ -47,9 +47,9 @@ the key=value pairs can change (e.g. "ONE TWO A=B C=D" or addition, the protocol is case-sensitive. Communication can take three distinct forms: -* Virtual streams -* Repliable datagrams (messages with a FROM field) -* Anonymous datagrams (raw anonymous messages) +* Virtual streams +* Repliable datagrams (messages with a FROM field) +* Anonymous datagrams (raw anonymous messages) ---------------------------------------------------------------------- SAM connection handshake @@ -401,8 +401,8 @@ Tunnel, I2CP, and Streaming Options These options may be passed in as name=value pairs at the end of a SAM SESSION CREATE line. -All sessions may include I2CP options such as tunnel lengths. -STREAM sessions may include Streaming lib options. +All sessions may include I2CP options such as tunnel lengths. +STREAM sessions may include Streaming lib options. See those references for option names and defaults. @@ -417,7 +417,7 @@ Base 64 encoding must use the I2P standard Base 64 alphabet "A-Z, a-z, 0-9, -, ~ Client library implementations: ---------------------------------------------------------------------- Client libraries are available for C, C++, C#, Perl, and Python. -These are in the apps/sam/ directory in the I2P Source Package. +These are in the apps/sam/ directory in the I2P Source Package. Some may be older and have not been updated for SAMv2 support. diff --git a/i2p2www/pages/site/docs/api/samv3.html b/i2p2www/pages/site/docs/api/samv3.html index 81db268f..5c46f858 100644 --- a/i2p2www/pages/site/docs/api/samv3.html +++ b/i2p2www/pages/site/docs/api/samv3.html @@ -56,9 +56,9 @@ messages sent by the client to the SAM bridge, and by "<- " for messages sent by the SAM bridge to the client. I2P communications can take three distinct forms: -* Virtual streams -* Repliable datagrams (messages with a FROM field) -* Anonymous datagrams (raw anonymous messages) +* Virtual streams +* Repliable datagrams (messages with a FROM field) +* Anonymous datagrams (raw anonymous messages) I2P communications are supported by I2P sessions, and each I2P session is bound to an address (called destination). An I2P session @@ -485,8 +485,8 @@ Tunnel, I2CP, and Streaming Options These options may be passed in as name=value pairs at the end of a SAM SESSION CREATE line. -All sessions may include I2CP options such as tunnel lengths. -STREAM sessions may include Streaming lib options. +All sessions may include I2CP options such as tunnel lengths. +STREAM sessions may include Streaming lib options. See those references for option names and defaults. @@ -501,7 +501,7 @@ Base 64 encoding must use the I2P standard Base 64 alphabet "A-Z, a-z, 0-9, -, ~ Client library implementations: ---------------------------------------------------------------------- Client libraries are available for C, C++, C#, Perl, and Python. -These are in the apps/sam/ directory in the I2P Source Package. +These are in the apps/sam/ directory in the I2P Source Package. Some may be older and have not been updated for SAMv3 support. diff --git a/i2p2www/pages/site/docs/api/streaming.html b/i2p2www/pages/site/docs/api/streaming.html index b6d5601d..a7c60e2a 100644 --- a/i2p2www/pages/site/docs/api/streaming.html +++ b/i2p2www/pages/site/docs/api/streaming.html @@ -67,7 +67,7 @@ streaming library, to be interpreted by I2CP.

    {% trans i2cp=site_url('docs/protocol/i2cp'), i2psktmf='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSocketManagerFactory.html', i2psktm='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSocketManager.html', -i2psess='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSession.html', +i2psess='http://docs.i2p-projekt.de/javadoc/net/i2p/client/I2PSession.html', i2pskt='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PSocket.html', i2psskt='http://docs.i2p-projekt.de/javadoc/net/i2p/client/streaming/I2PServerSocket.html' -%} The standard interface to the streaming lib is for the application to use the diff --git a/i2p2www/pages/site/docs/applications/supported.html b/i2p2www/pages/site/docs/applications/supported.html index 52f0ce66..f454e644 100644 --- a/i2p2www/pages/site/docs/applications/supported.html +++ b/i2p2www/pages/site/docs/applications/supported.html @@ -197,7 +197,7 @@ shortcuts. -->

  • -

    El Dorado — +

    El Dorado — {% trans %}Lightweight forum software.{% endtrans %} [{{ _('standalone/mod') }}]

    • @@ -209,7 +209,7 @@ shortcuts.
  • -

    phpBB — +

    phpBB — {% trans %}Most popular open source forum software.{% endtrans %} [{{ _('standalone/mod') }}]

    • @@ -253,7 +253,7 @@ distributed file system to the I2P network. Controller plugin
  • -

    Monotone — +

    Monotone — {% trans monotone=site_url('get-involved/guides/monotone') -%} Another distributed version control system. Currently used in I2P development. @@ -407,7 +407,7 @@ branch of the I2P Monotone repository.

  • I2Phex — {% trans stats=i2pconv('stats.i2p') -%} -Port of the Phex Gnutella client. Website +Port of the Phex Gnutella client. Website for plugin version here. {%- endtrans %} [{{ _('plugin') }}, {{ _('standalone') }}]

    @@ -502,7 +502,7 @@ developers; they may be able to solve it via additional filtering.
    • -

      jIRCii — +

      jIRCii — {% trans stats=i2pconv('stats.i2p') -%} Small Java-based IRC client. Plugin available here. @@ -694,7 +694,7 @@ currently serve content on the I2P network are:

    • -

      nginx — +

      nginx — {% trans %}High-performance lightweight web server.{% endtrans %} [{{ _('standalone') }}]

      • diff --git a/i2p2www/pages/site/docs/discussions/netdb.html b/i2p2www/pages/site/docs/discussions/netdb.html index ab3769b4..55b8c9fc 100644 --- a/i2p2www/pages/site/docs/discussions/netdb.html +++ b/i2p2www/pages/site/docs/discussions/netdb.html @@ -3,7 +3,7 @@ {% block content %}

      NOTE: The following is a discussion of the history of netdb implementation and is not current information. -See the main netdb page for current documentation. +See the main netdb page for current documentation.

      History

      @@ -241,7 +241,7 @@ This just accounts for the stores - what about the queries?

      The Return of the Kademlia Algorithm?

      -(this is adapted from the I2P meeting Jan. 2, 2007) +(this is adapted from the I2P meeting Jan. 2, 2007)
      The Kademlia netDb just wasn't working properly. Is it dead forever or will it be coming back? @@ -282,7 +282,7 @@ Not necessarily DHT-based.

      Floodfill TODO List

      NOTE: The following is not current information. -See the main netdb page for the current status and a list of future work. +See the main netdb page for the current status and a list of future work.

      The network was down to only one floodfill for a couple of hours on March 13, 2008 (approx. 18:00 - 20:00 UTC), @@ -365,7 +365,7 @@ we are now at the minimum number of stats required to monitor the network.

    • [In Release 0.6.3] Manual list of floodfill peers to exclude? -(blocklists by router ident) +(blocklists by router ident)
    • [In Release 0.6.3] Better floodfill peer selection for stores: diff --git a/i2p2www/pages/site/docs/how/cryptography.html b/i2p2www/pages/site/docs/how/cryptography.html index 93b2e2c0..c0bb0602 100644 --- a/i2p2www/pages/site/docs/how/cryptography.html +++ b/i2p2www/pages/site/docs/how/cryptography.html @@ -142,7 +142,8 @@ Using 2 as the generator.

      {% trans %}Short Exponent{% endtrans %}

      {% trans commonstructures=site_url('docs/spec/common-structures'), pdf='http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.14.5952&rep=rep1&type=pdf', -benchmarks=site_url('misc/benchmarks') -%} +benchmarks=site_url('misc/benchmarks'), +oldbenchmarks='http://www.eskimo.com/~weidai/benchmarks.html' -%} While the standard exponent size is 2048 bits (256 bytes) and the I2P PrivateKey is a full 256 bytes, @@ -150,7 +151,7 @@ we use the short exponent size of 226 bits (28.25 bytes). This should be safe for use with the Oakley primes, per On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner at EuroCrypt 96, and crypto++'s benchmarks. -Benchmarks originally at this link, now dead, +Benchmarks originally at {{ oldbenchmarks }} (now dead), rescued from the wayback machine, dated Apr 23, 2008. {%- endtrans %}

      diff --git a/i2p2www/pages/site/docs/how/garlic-routing.html b/i2p2www/pages/site/docs/how/garlic-routing.html index 767b2018..f98d6f91 100644 --- a/i2p2www/pages/site/docs/how/garlic-routing.html +++ b/i2p2www/pages/site/docs/how/garlic-routing.html @@ -15,7 +15,7 @@ the usage of "garlic" methods in I2P. Michael J. Freedman in Roger Dingledine's Free Haven Master's thesis Section 8.1.1 (June 2000), as derived from -Onion Routing. +Onion Routing. {%- endtrans %}

      {% trans -%} diff --git a/i2p2www/pages/site/docs/how/intro.html b/i2p2www/pages/site/docs/how/intro.html index a9374630..93ec5cc1 100644 --- a/i2p2www/pages/site/docs/how/intro.html +++ b/i2p2www/pages/site/docs/how/intro.html @@ -151,10 +151,11 @@ the network (N) bears no impact. {%- endtrans %}

      {% trans %}When?{% endtrans %}

      -

      {% trans roadmap=site_url('get-involved/roadmap') -%} +

      {% trans roadmap=site_url('get-involved/roadmap'), +jms='http://www.oracle.com/technetwork/java/jms/index.html' -%} I2P initially began in Feb 2003 as a proposed modification to Freenet to allow it to use alternate transports, such as JMS, then grew into its own as an +href="{{ jms }}">JMS, then grew into its own as an 'anonCommFramework' in April 2003, turning into I2P in July, with code being written in earnest starting in August '03. I2P is currently under development, following the roadmap. diff --git a/i2p2www/pages/site/docs/how/network-database.html b/i2p2www/pages/site/docs/how/network-database.html index 4c677a7b..45bde67c 100644 --- a/i2p2www/pages/site/docs/how/network-database.html +++ b/i2p2www/pages/site/docs/how/network-database.html @@ -747,7 +747,7 @@ for a discussion of the vulnerabilities of peer selection for tunnels. {%- endtrans %}

      {% trans %}Information Leaks{% endtrans %}

      -

      {% trans pdf='https://netfiles.uiuc.edu/mittal2/www/nisan-torsk-ccs10.pdf' -%} +

      {% trans pdf='http://www.eecs.berkeley.edu/~pmittal/publications/nisan-torsk-ccs10.pdf' -%} (Reference: In Search of an Anonymous and Secure Lookup Section 3) {%- endtrans %}

      diff --git a/i2p2www/pages/site/docs/how/peer-selection.html b/i2p2www/pages/site/docs/how/peer-selection.html index 2537ef3e..fd26f061 100644 --- a/i2p2www/pages/site/docs/how/peer-selection.html +++ b/i2p2www/pages/site/docs/how/peer-selection.html @@ -250,8 +250,8 @@ Peers for which a recent connection attempt failed are not used.

      {% trans %}Peer Ordering in Tunnels{% endtrans %}

      -

      {% trans pdf='http://prisms.cs.umass.edu/brian/pubs/wright-tissec.pdf', -pdf2008='http://prisms.cs.umass.edu/brian/pubs/wright.tissec.2008.pdf', +

      {% trans pdf='http://forensics.umass.edu/pubs/wright-tissec.pdf', +pdf2008='http://forensics.umass.edu/pubs/wright.tissec.2008.pdf', tunnelimpl=site_url('docs/tunnels/implementation') -%} Peers are ordered within tunnels to to deal with the predecessor attack @@ -306,7 +306,7 @@ please keep in mind the following minor changes in I2P since the paper's publica

    • {% trans %}Tune-up for Tor{% endtrans %}
    • -{% trans %}Low-resource Routing Attacks Against Tor{% endtrans %} +{% trans %}Low-resource Routing Attacks Against Tor{% endtrans %}
    {% endblock %} diff --git a/i2p2www/pages/site/docs/how/threat-model.html b/i2p2www/pages/site/docs/how/threat-model.html index 09d3c402..33f1cd35 100644 --- a/i2p2www/pages/site/docs/how/threat-model.html +++ b/i2p2www/pages/site/docs/how/threat-model.html @@ -431,7 +431,7 @@ matter, the attacker would need to control a significant portion of the network which other tunnels or messages have those delays). {%- endtrans %}

    -

    {% trans netdb=site_url('docs/how/networkdatabase') -%} +

    {% trans netdb=site_url('docs/how/network-database') -%} Also discussed on the network database page (bootstrap attack). {%- endtrans %}

    @@ -470,8 +470,8 @@ was specifically designed to combat the predecessor attack. See also the intersection attack. {%- endtrans %}

    -

    {% trans pdf2008='http://prisms.cs.umass.edu/brian/pubs/wright.tissec.2008.pdf', -pdf2004='http://prisms.cs.umass.edu/brian/pubs/wright-tissec.pdf' -%} +

    {% trans pdf2008='http://forensics.umass.edu/pubs/wright.tissec.2008.pdf', +pdf2004='http://forensics.umass.edu/pubs/wright-tissec.pdf' -%} References: {{ pdf2008 }} which is an update to the 2004 predecessor attack paper {{ pdf2004 }}. @@ -627,7 +627,7 @@ for more Sybil discussion.

    {% trans %}Buddy Exhaustion attacks{% endtrans %}

    -

    {% trans pdf='https://netfiles.uiuc.edu/mittal2/www/nisan-torsk-ccs10.pdf' -%} +

    {% trans pdf='http://www.eecs.berkeley.edu/~pmittal/publications/nisan-torsk-ccs10.pdf' -%} (Reference: In Search of an Anonymouns and Secure Lookup Section 5.2) {%- endtrans %}

    diff --git a/i2p2www/pages/site/docs/index.html b/i2p2www/pages/site/docs/index.html index 5f8a2341..5b860b55 100644 --- a/i2p2www/pages/site/docs/index.html +++ b/i2p2www/pages/site/docs/index.html @@ -227,7 +227,7 @@ Traditionally used only by Java applications and higher-level APIs.
  • {{ _('Source translation at Transifex') }}
  • -{{ _('0.9 roadmap wiki') }} ({{ _('not current') }}) +{{ _('Roadmap wiki') }}
  • {{ _('Old roadmap') }} ({{ _('not current') }})
  • diff --git a/i2p2www/pages/site/docs/spec/streaming.html b/i2p2www/pages/site/docs/spec/streaming.html index 05db8ba0..41e49de9 100644 --- a/i2p2www/pages/site/docs/spec/streaming.html +++ b/i2p2www/pages/site/docs/spec/streaming.html @@ -33,21 +33,21 @@ The format of a single packet in the streaming protocol is:
    {{ _('Field') }}{{ _('Length') }}{{ _('Contents') }} -
    sendStreamId 4 byte IntegerRandom number selected by the connection recipient +
    sendStreamId 4 byte IntegerRandom number selected by the connection recipient and constant for the life of the connection. 0 in the SYN message sent by the originator, and in subsequent messages, until a SYN reply is received, containing the peer's stream ID. -
    receiveStreamId 4 byte IntegerRandom number selected by the connection originator +
    receiveStreamId 4 byte IntegerRandom number selected by the connection originator and constant for the life of the connection. May be 0 if unknown, for example in a RESET packet. -
    sequenceNum 4 byte Integer +
    sequenceNum 4 byte Integer The sequence for this message, starting at 0 in the SYN message, and incremented by 1 in each message except for plain ACKs and retransmissions. If the sequenceNum is 0 and the SYN flag is not set, this is a plain ACK packet that should not be ACKed. -
    ackThrough 4 byte Integer +
    ackThrough 4 byte Integer The highest packet sequence number that was received on the receiveStreamId. This field is ignored on the initial connection packet (where receiveStreamId is the unknown id) or @@ -55,14 +55,14 @@ if the NO_ACK flag set. All packets up to and including this sequence number are ACKed, EXCEPT for those listed in NACKs below. -
    NACK count1 byte Integer +
    NACK count1 byte Integer The number of 4-byte NACKs in the next field -
    NACKs n * 4 byte Integers +
    NACKs n * 4 byte Integers Sequence numbers less than ackThrough that are not yet received. Two NACKs of a packet is a request for a 'fast retransmit' of that packet. -
    resendDelay1 byte Integer +
    resendDelay1 byte Integer How long is the creator of this packet going to wait before resending this packet (if it hasn't yet been ACKed). The value is seconds since the packet was created. @@ -71,7 +71,7 @@ Currently ignored on receive.
    flags 2 byte value See below. -
    option size2 byte Integer +
    option size2 byte Integer The number of bytes in the next field
    option data0 or more bytes @@ -103,23 +103,23 @@ SIGNATURE_INCLUDED must be set also.
    2RESET-- Abnormal close. SIGNATURE_INCLUDED must be set also. -
    3SIGNATURE_INCLUDED40 byte DSA Signature +
    3SIGNATURE_INCLUDED40 byte DSA Signature Currently sent only with SYNCHRONIZE, CLOSE, and RESET, where it is required. -The signature uses the Destination's DSA signing keys +The signature uses the Destination's DSA signing keys to sign the entire header and payload with the 40-byte space in the option data field for the signature being set to all zeroes.
    4SIGNATURE_REQUESTED-- Unused. Requests every packet in the other direction to have SIGNATURE_INCLUDED -
    5FROM_INCLUDED387+ byte Destination +
    5FROM_INCLUDED387+ byte Destination Currently sent only with SYNCHRONIZE, where it is required. -
    6DELAY_REQUESTED2 byte Integer +
    6DELAY_REQUESTED2 byte Integer Optional delay. How many milliseconds the sender of this packet wants the recipient to wait before sending any more data. A value greater than 60000 indicates choking. -
    7MAX_PACKET_SIZE_INCLUDED2 byte Integer +
    7MAX_PACKET_SIZE_INCLUDED2 byte Integer Currently sent with SYNCHRONIZE only. Was also sent in retransmitted packets until release 0.9.1.
    8PROFILE_INTERACTIVE--