I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Assorted internal and external URL fixes

Browse Source
This commit is contained in:
str4d
2013-02-06 01:55:33 +00:00
parent d5a8e1b958
commit b455e878c7
23 changed files with 80 additions and 77 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
i2p2www/pages/site/about/browser-config.html
View File

@ -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 %}</p>
<p>{% trans -%}
<p>{% 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 <a href="http://tbp.i2p">tpb.i2p</a>. Eepsites
they host an official eepsite at <a href="http://{{ tpb }}">{{ tpb }}</a>. Eepsites
that are accessible via .i2p addresses are also not allowed via the outproxies.
As a convenience, <code>False.i2p</code> blocks ad servers.
{%- endtrans %}</p>

6
i2p2www/pages/site/about/hall-of-fame.html
View File

@ -14,11 +14,11 @@ Current balance: as of {{ date }}
{% trans euroval='100.0' %}{{ euroval }} &euro;{% endtrans %}</b><br />
<b><a href="{{ site_url('get-involved/bounties/i2phex') }}">{{ _('I2PHex bounty') }}</a>:
{% trans euroval='60.0' %}{{ euroval }} &euro;{% endtrans %}</b><br />
<b><a href="{{ site_url('get-involved/bounties/debpack') }}">{{ _('I2P in debian mirrors') }}</a>:
<b><a href="{{ site_url('get-involved/bounties/deb-pack') }}">{{ _('I2P in debian mirrors') }}</a>:
{% trans euroval='113.0' %}{{ euroval }} &euro;{% endtrans %}</b><br />
<b><a href="{{ site_url('get-involved/bounties/btcclient') }}">{{ _('Bitcoin client for I2P') }}</a>:
<b><a href="{{ site_url('get-involved/bounties/btc-client') }}">{{ _('Bitcoin client for I2P') }}</a>:
{% trans euroval='30.0', btcval='118.34' %}{{ euroval }} &euro; and {{ btcval }} BTC{% endtrans %}</b><br />
<b><a href="{{ site_url('get-involved/bounties/unittests') }}">{{ _('Unit Tests for I2P router') }}</a>:
<b><a href="{{ site_url('get-involved/bounties/unit-tests') }}">{{ _('Unit Tests for I2P router') }}</a>:
{% trans euroval='2700' %}{{ euroval }} &euro;{% endtrans %}</b><br />
<b>{{ _('Bounty Robert') }}: 0</b><br />
<b>{{ _('Bounty Syndie') }}: 100 BTC</b><br />

4
i2p2www/pages/site/about/intro.html
View File

@ -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
<a href="http://bitconjurer.org/BitTorrent/">BitTorrent</a>), a
distributed data store (a la <a href="http://freenetproject.org/">Freenet</a> /
<a href="http://www.bittorrent.com/">BitTorrent</a>), a
distributed data store (a la <a href="https://freenetproject.org/">Freenet</a> /
<a href="http://mnetproject.org/">MNet</a>), and a blogging system (a fully
distributed <a href="http://www.livejournal.com/">LiveJournal</a>), but those are
not ready for use yet.

5
i2p2www/pages/site/about/performance/history.html
View File

@ -9,13 +9,14 @@ for current issues and thoughts.
<h2>{{ _('Native math') }}</h2>
<b>[{{ _('implemented') }}]</b>
<p>{% trans modpow='http://java.sun.com/j2se/1.4.2/docs/api/java/math/BigInteger.html#modPow(java.math.BigInteger,%20java.math.BigInteger)',
<p>{% 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
<a href="{{ modpow }}">modPow</a>.
Rather than try to tune this method, we'll call out to
<a href="http://www.swox.com/gmp/">GNU MP</a> - an insanely fast math library
<a href="{{ gmp }}">GNU MP</a> - an insanely fast math library
(with tuned assembler for many architectures). (<i>Editor: see
<a href="{{ jbigi }}">NativeBigInteger for faster public key cryptography</a></i>)
{%- endtrans %}</p>

2
i2p2www/pages/site/about/team.html
View File

@ -37,7 +37,7 @@ network.
<td valign="top"><i>{{ _('manage the project mirrors') }}</i></td>
</tr>
<tr>
<td valign="top"><b>{% trans monotone=site_url('get-involved/develop/monotone') %}<a href="{{ monotone }}">Monotone</a> guru{% endtrans %}</b></td>
<td valign="top"><b>{% trans monotone=site_url('get-involved/guides/monotone') %}<a href="{{ monotone }}">Monotone</a> guru{% endtrans %}</b></td>
<td valign="top">welterde, eche|on</td>
<td valign="top"><i>{{ _('manage the public monotone repositories') }}</i></td>
</tr>

4
i2p2www/pages/site/comparison/freenet.html
View File

@ -13,7 +13,7 @@ built applications on top of it to do more generic anonymous communication, such
static websites and message boards.
{%- endtrans %}</p>
<p>{% trans -%}
<p>{% 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 <a href="http://tahoe-lafs.org/trac/tahoe-lafs">Tahoe-LAFS</a>)
(most recently a port of <a href="{{ tahoe }}">Tahoe-LAFS</a>)
but nothing is yet ready for general use.
{%- endtrans %}</p>

14
i2p2www/pages/site/comparison/other-networks.html
View File

@ -23,8 +23,8 @@ You may contribute an analysis by entering a
<h2>Morphmix / Tarzan</h2>
<i><a href="http://www.tik.ee.ethz.ch/~morphmix/">[Morphmix]</a>
<a href="http://www.pdos.lcs.mit.edu/tarzan/">[Tarzan]</a></i>
<i><a href="https://home.zhaw.ch/~rer/projects/morphmix/">[Morphmix]</a>
<a href="http://pdos.csail.mit.edu/tarzan/">[Tarzan]</a></i>
<p>{% 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.
<h2>JAP</h2>
<i><a href="http://anon.inf.tu-dresden.de/index_en.html">[JAP]</a></i>
<p>{% trans -%}
<p>{% 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
<a href="http://www.datenschutzzentrum.de/material/themen/presse/anonip3_e.htm">attack</a>
<a href="{{ url }}">attack</a>
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)
<h2>MUTE / AntsP2P</h2>
<i><a href="http://mute-net.sourceforge.net/">[MUTE]</a>
<a href="http://www.myjavaserver.com/~gwren/home.jsp?page=custom&xmlName=ants">[AntsP2P]</a></i>
<a href="http://antsp2p.sourceforge.net/">[AntsP2P]</a></i>
<p>{% trans -%}
<p>{% trans antnet='http://citeseer.ist.psu.edu/57701.html' -%}
Both of these systems work through the same basic
<a href="http://citeseer.ist.psu.edu/57701.html">antnet</a> routing, providing some degree of
<a href="{{ antnet }}">antnet</a> 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

2
i2p2www/pages/site/contact.html
View File

@ -4,7 +4,7 @@
<h1>IRC</h1>
<p>{% 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 <a href="https://www.oftc.net/oftc/">OFTC</a>,
We are also present on multiple standard networks like <a href="http://www.oftc.net/oftc/OFTC">OFTC</a>,
<a href="http://www.einirc.de/">EIN</a> and <a href="http://freenode.net/">Freenode</a>.
All I2P-related channels on all these network are linked to the main channels on Irc2P via relay bots.
{%- endtrans %}</p>

2
i2p2www/pages/site/docs/api/i2pcontrol.html
View File

@ -57,7 +57,7 @@ Parameters are only provided in a named way (maps).
</ul>
<ul>GetRate &ndash; {% trans %}Fetches rateStat from router statManager. Creates stat if not already created.{% endtrans %}
<ul>{{ _('Request:') }}
<li>Stat &ndash; [String] {% trans %}Determines which rateStat to fetch, see <a href="ratestats.html">ratestats</a>.{% endtrans %}</li>
<li>Stat &ndash; [String] {% trans ratestats=site_url('misc/ratestats') %}Determines which rateStat to fetch, see <a href="{{ ratestats }}">ratestats</a>.{% endtrans %}</li>
<li>Period &ndash; [long] {% trans %}Determines which period a stat is fetched for. Measured in ms.{% endtrans %}</li>
<li>Token &ndash; [String] {% trans %}Token used for authenticating the client. Is provided by the server via the 'Authenticate' RPC method.{% endtrans %}</li>
</ul>

12
i2p2www/pages/site/docs/api/sam.html
View File

@ -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:
* <a href="streaming.html">Virtual streams</a>
* <a href="datagrams.html#repliable">Repliable datagrams</a> (messages with a FROM field)
* <a href="datagrams.html#raw">Anonymous datagrams</a> (raw anonymous messages)
* <a href="{{ site_url('docs/api/streaming') }}">Virtual streams</a>
* <a href="{{ site_url('docs/spec/datagrams') }}#repliable">Repliable datagrams</a> (messages with a FROM field)
* <a href="{{ site_url('docs/spec/datagrams') }}#raw">Anonymous datagrams</a> (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 <a href="i2cp.html#options">I2CP options such as tunnel lengths</a>.
STREAM sessions may include <a href="streaming.html#options">Streaming lib options</a>.
All sessions may include <a href="{{ site_url('docs/protocol/i2cp') }}#options">I2CP options such as tunnel lengths</a>.
STREAM sessions may include <a href="{{ site_url('docs/api/streaming') }}#options">Streaming lib options</a>.
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 <a href="download.html">I2P Source Package</a>.
These are in the apps/sam/ directory in the <a href="{{ get_url('downloads_list') }}">I2P Source Package</a>.
----------------------------------------------------------------------

12
i2p2www/pages/site/docs/api/samv2.html
View File

@ -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:
* <a href="streaming.html">Virtual streams</a>
* <a href="datagrams.html#repliable">Repliable datagrams</a> (messages with a FROM field)
* <a href="datagrams.html#raw">Anonymous datagrams</a> (raw anonymous messages)
* <a href="{{ site_url('docs/api/streaming') }}">Virtual streams</a>
* <a href="{{ site_url('docs/spec/datagrams') }}#repliable">Repliable datagrams</a> (messages with a FROM field)
* <a href="{{ site_url('docs/spec/datagrams') }}#raw">Anonymous datagrams</a> (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 <a href="i2cp.html#options">I2CP options such as tunnel lengths</a>.
STREAM sessions may include <a href="streaming.html#options">Streaming lib options</a>.
All sessions may include <a href="{{ site_url('docs/protocol/i2cp') }}#options">I2CP options such as tunnel lengths</a>.
STREAM sessions may include <a href="{{ site_url('docs/api/streaming') }}#options">Streaming lib options</a>.
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 <a href="download.html">I2P Source Package</a>.
These are in the apps/sam/ directory in the <a href="{{ get_url('downloads_list') }}">I2P Source Package</a>.
Some may be older and have not been updated for SAMv2 support.

12
i2p2www/pages/site/docs/api/samv3.html
View File

@ -56,9 +56,9 @@ messages sent by the client to the SAM bridge, and by "&lt;- " for
messages sent by the SAM bridge to the client.
I2P communications can take three distinct forms:
* <a href="streaming.html">Virtual streams</a>
* <a href="datagrams.html#repliable">Repliable datagrams</a> (messages with a FROM field)
* <a href="datagrams.html#raw">Anonymous datagrams</a> (raw anonymous messages)
* <a href="{{ site_url('docs/api/streaming') }}">Virtual streams</a>
* <a href="{{ site_url('docs/spec/datagrams') }}#repliable">Repliable datagrams</a> (messages with a FROM field)
* <a href="{{ site_url('docs/spec/datagrams') }}#raw">Anonymous datagrams</a> (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 <a href="i2cp.html#options">I2CP options such as tunnel lengths</a>.
STREAM sessions may include <a href="streaming.html#options">Streaming lib options</a>.
All sessions may include <a href="{{ site_url('docs/protocol/i2cp') }}#options">I2CP options such as tunnel lengths</a>.
STREAM sessions may include <a href="{{ site_url('docs/api/streaming') }}#options">Streaming lib options</a>.
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 <a href="download.html">I2P Source Package</a>.
These are in the apps/sam/ directory in the <a href="{{ get_url('downloads_list') }}">I2P Source Package</a>.
Some may be older and have not been updated for SAMv3 support.

2
i2p2www/pages/site/docs/api/streaming.html
View File

@ -67,7 +67,7 @@ streaming library, to be interpreted by I2CP.
<p>{% 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

12
i2p2www/pages/site/docs/applications/supported.html
View File

@ -197,7 +197,7 @@ shortcuts.
-->
<li>
<p><a href="http://github.com/trevorturk/eldorado/"><strong>El Dorado</strong></a> —
<p><a href="https://github.com/trevorturk/eldorado/"><strong>El Dorado</strong></a> —
{% trans %}Lightweight forum software.{% endtrans %}
<sup><em>[{{ _('standalone/mod') }}]</em></sup></p>
</li>
@ -209,7 +209,7 @@ shortcuts.
</li>
<li>
<p><a href="http://www.phpbb.com/"><strong>phpBB</strong></a> —
<p><a href="https://www.phpbb.com/"><strong>phpBB</strong></a> —
{% trans %}Most popular open source forum software.{% endtrans %}
<sup><em>[{{ _('standalone/mod') }}]</em></sup></p>
</li>
@ -253,7 +253,7 @@ distributed file system to the I2P network. Controller plugin <a href=
</li>
<li>
<p><a href="http://monotone.ca/"><strong>Monotone</strong></a> —
<p><a href="http://www.monotone.ca/"><strong>Monotone</strong></a> —
{% trans monotone=site_url('get-involved/guides/monotone') -%}
Another distributed version control system. Currently
<a href="{{ monotone }}">used in I2P development</a>.
@ -407,7 +407,7 @@ branch of the <a href="{{ newdevs }}">I2P Monotone repository</a>.
<li>
<p><a href="http://{{ i2pconv('forum.i2p') }}/viewforum.php?f=25"><strong>I2Phex</strong></a> —
{% trans stats=i2pconv('stats.i2p') -%}
Port of the <a href="http://www.phex.org/">Phex</a> Gnutella client. Website
Port of the <a href="http://www.phex.org/mambo/">Phex</a> Gnutella client. Website
for plugin version <a href="http://{{ stats }}/i2p/plugins/">here</a>.
{%- endtrans %}
<sup><em>[{{ _('plugin') }},&nbsp;{{ _('standalone') }}]</em></sup></p>
@ -502,7 +502,7 @@ developers; they may be able to solve it via additional filtering.
<ul>
<li>
<p><a href="http://jircii.dashnine.org/"><strong>jIRCii</strong></a> —
<p><a href="http://www.oldschoolirc.com/"><strong>jIRCii</strong></a> —
{% trans stats=i2pconv('stats.i2p') -%}
Small Java-based IRC client. Plugin available <a href=
"http://{{ stats }}/i2p/plugins/">here</a>.
@ -694,7 +694,7 @@ currently serve content on the I2P network are:
</li>
<li>
<p><a href="http://www.nginx.org/"><strong>nginx</strong></a> —
<p><a href="http://nginx.org/"><strong>nginx</strong></a> —
{% trans %}High-performance lightweight web server.{% endtrans %}
<sup><em>[{{ _('standalone') }}]</em></sup></p>
</li>

8
i2p2www/pages/site/docs/discussions/netdb.html
View File

@ -3,7 +3,7 @@
{% block content %}
<p>
NOTE: The following is a discussion of the history of netdb implementation and is not current information.
See <a href="{{ site_url('docs/how/networkdatabase') }}">the main netdb page</a> for current documentation</a>.
See <a href="{{ site_url('docs/how/network-database') }}">the main netdb page</a> for current documentation</a>.
<h2><a name="status">History</a></h2>
@ -241,7 +241,7 @@ This just accounts for the stores - what about the queries?
<h3>The Return of the Kademlia Algorithm?</h3>
<p>
(this is adapted from <a href="{{ url_for('meetings_show', id=195) }}">the I2P meeting Jan. 2, 2007</a>)
(this is adapted from <a href="{{ get_url('meetings_show', id=195) }}">the I2P meeting Jan. 2, 2007</a>)
<br />
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.
<h3 id="todo">Floodfill TODO List</h3>
<p>
NOTE: The following is not current information.
See <a href="{{ site_url('docs/how/networkdatabase') }}">the main netdb page</a> for the current status and a list of future work</a>.
See <a href="{{ site_url('docs/how/network-database') }}">the main netdb page</a> for the current status and a list of future work</a>.
<p>
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.
<li>
[In Release 0.6.3]
Manual list of floodfill peers to exclude?
(<a href="{{ site_url('docs/how/threatmodel') }}#blocklist">blocklists</a> by router ident)
(<a href="{{ site_url('docs/how/threat-model') }}#blocklist">blocklists</a> by router ident)
<li>
[In Release 0.6.3]
Better floodfill peer selection for stores:

5
i2p2www/pages/site/docs/how/cryptography.html
View File

@ -142,7 +142,8 @@ Using 2 as the generator.
<h3>{% trans %}Short Exponent{% endtrans %}</h3>
<p>{% trans commonstructures=site_url('docs/spec/common-structures'),
pdf='http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.14.5952&amp;rep=rep1&amp;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
<a href="{{ commonstructures }}#type_PrivateKey">PrivateKey</a>
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
<a href="{{ pdf }}">On Diffie-Hellman Key Agreement with Short Exponents - van Oorschot, Weiner</a>
at EuroCrypt 96, and <a href="{{ benchmarks }}">crypto++'s benchmarks</a>.
Benchmarks originally at <a rel="nofollow" href="http://www.eskimo.com/~weidai/benchmarks.html">this link, now dead</a>,
Benchmarks originally at <code>{{ oldbenchmarks }}</code> (now dead),
rescued from <a href="http://www.archive.org/">the wayback machine</a>, dated Apr 23, 2008.
{%- endtrans %}</p>

2
i2p2www/pages/site/docs/how/garlic-routing.html
View File

@ -15,7 +15,7 @@ the usage of "garlic" methods in I2P.
<a href="http://www.cs.princeton.edu/~mfreed/">Michael J. Freedman</a>
in Roger Dingledine's Free Haven
<a href="http://www.freehaven.net/papers.html">Master's thesis</a> Section 8.1.1 (June 2000), as derived from
<a href="http://onion-router.net/">Onion Routing</a>.
<a href="http://www.onion-router.net/">Onion Routing</a>.
{%- endtrans %}</p>
<p>{% trans -%}

5
i2p2www/pages/site/docs/how/intro.html
View File

@ -151,10 +151,11 @@ the network (N) bears no impact.
{%- endtrans %}</p>
<h2>{% trans %}When?{% endtrans %}</h2>
<p>{% trans roadmap=site_url('get-involved/roadmap') -%}
<p>{% 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 <a
href="http://freenetproject.org">Freenet</a> to allow it to use alternate transports, such as <a
href="http://java.sun.com/products/jms/index.jsp">JMS</a>, then grew into its own as an
href="{{ jms }}">JMS</a>, 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 <a href="{{ roadmap
}}">roadmap</a>.

2
i2p2www/pages/site/docs/how/network-database.html
View File

@ -747,7 +747,7 @@ for a discussion of the vulnerabilities of peer selection for tunnels.
{%- endtrans %}</p>
<h3>{% trans %}Information Leaks{% endtrans %}</h3>
<p>{% trans pdf='https://netfiles.uiuc.edu/mittal2/www/nisan-torsk-ccs10.pdf' -%}
<p>{% trans pdf='http://www.eecs.berkeley.edu/~pmittal/publications/nisan-torsk-ccs10.pdf' -%}
(Reference: <a href="{{ pdf }}">In Search of an Anonymous and Secure Lookup</a> Section 3)
{%- endtrans %}</p>

6
i2p2www/pages/site/docs/how/peer-selection.html
View File

@ -250,8 +250,8 @@ Peers for which a recent connection attempt failed are not used.
<h3>{% trans %}Peer Ordering in Tunnels{% endtrans %}</h3>
<p>{% trans pdf='http://prisms.cs.umass.edu/brian/pubs/wright-tissec.pdf',
pdf2008='http://prisms.cs.umass.edu/brian/pubs/wright.tissec.2008.pdf',
<p>{% 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 <a href="{{ pdf }}">predecessor attack</a>
@ -306,7 +306,7 @@ please keep in mind the following minor changes in I2P since the paper's publica
<li>
<a href="http://www.crhc.uiuc.edu/~nikita/papers/tuneup-cr.pdf">{% trans %}Tune-up for Tor{% endtrans %}</a>
<li>
<a href="http://systems.cs.colorado.edu/~bauerk/papers/wpes25-bauer.pdf">{% trans %}Low-resource Routing Attacks Against Tor{% endtrans %}</a>
<a href="http://cs.gmu.edu/~mccoy/papers/wpes25-bauer.pdf">{% trans %}Low-resource Routing Attacks Against Tor{% endtrans %}</a>
</ul>
{% endblock %}

8
i2p2www/pages/site/docs/how/threat-model.html
View File

@ -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 %}</p>
<p>{% trans netdb=site_url('docs/how/networkdatabase') -%}
<p>{% trans netdb=site_url('docs/how/network-database') -%}
Also discussed on the <a href="{{ netdb }}#threat">network database page</a> (bootstrap attack).
{%- endtrans %}</p>
@ -470,8 +470,8 @@ was specifically designed to combat the predecessor attack.
See also <a href="#intersection">the intersection attack</a>.
{%- endtrans %}</p>
<p>{% trans pdf2008='http://prisms.cs.umass.edu/brian/pubs/wright.tissec.2008.pdf',
pdf2004='http://prisms.cs.umass.edu/brian/pubs/wright-tissec.pdf' -%}
<p>{% trans pdf2008='http://forensics.umass.edu/pubs/wright.tissec.2008.pdf',
pdf2004='http://forensics.umass.edu/pubs/wright-tissec.pdf' -%}
References: <a href="{{ pdf2008 }}">{{ pdf2008 }}</a>
which is an update to the 2004 predecessor attack paper
<a href="{{ pdf2004 }}">{{ pdf2004 }}</a>.
@ -627,7 +627,7 @@ for more Sybil discussion.
<h3 id="buddy">{% trans %}Buddy Exhaustion attacks{% endtrans %}</h3>
<p>{% trans pdf='https://netfiles.uiuc.edu/mittal2/www/nisan-torsk-ccs10.pdf' -%}
<p>{% trans pdf='http://www.eecs.berkeley.edu/~pmittal/publications/nisan-torsk-ccs10.pdf' -%}
(Reference: <a href="{{ pdf }}">In Search of an Anonymouns and Secure Lookup</a> Section 5.2)
{%- endtrans %}</p>

2
i2p2www/pages/site/docs/index.html
View File

@ -227,7 +227,7 @@ Traditionally used only by Java applications and higher-level APIs.
</li><li>
<a href="https://www.transifex.net/projects/p/I2P/">{{ _('Source translation at Transifex') }}</a>
</li><li>
<a href="http://{{ i2pconv('trac.i2p2.i2p') }}/09roadmap">{{ _('0.9 roadmap wiki') }}</a> ({{ _('not current') }})
<a href="http://{{ i2pconv('trac.i2p2.i2p') }}/wiki/Roadmaps/1.0">{{ _('Roadmap wiki') }}</a>
</li><li>
<a href="{{ site_url('get-involved/roadmap') }}">{{ _('Old roadmap') }}</a> ({{ _('not current') }})
</li><li>

26
i2p2www/pages/site/docs/spec/streaming.html
View File

@ -33,21 +33,21 @@ The format of a single packet in the streaming protocol is:
<table>
<tr><th>{{ _('Field') }}<th>{{ _('Length') }}<th>{{ _('Contents') }}
<tr><td>sendStreamId <td>4 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>Random number selected by the connection recipient
<tr><td>sendStreamId <td>4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>Random 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.
<tr><td>receiveStreamId <td>4 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>Random number selected by the connection originator
<tr><td>receiveStreamId <td>4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>Random 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.
<tr><td>sequenceNum <td>4 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>
<tr><td>sequenceNum <td>4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>
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.
<tr><td>ackThrough <td>4 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>
<tr><td>ackThrough <td>4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>
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.
<tr><td>NACK count<td>1 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>
<tr><td>NACK count<td>1 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>
The number of 4-byte NACKs in the next field
<tr><td>NACKs <td>n * 4 byte <a href="common_structures_spec.html#type_Integer">Integers</a><td>
<tr><td>NACKs <td>n * 4 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integers</a><td>
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.
<tr><td>resendDelay<td>1 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>
<tr><td>resendDelay<td>1 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>
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.
<tr><td>flags <td>2 byte value<td>
See below.
<tr><td>option size<td>2 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>
<tr><td>option size<td>2 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>
The number of bytes in the next field
<tr><td>option data<td>0 or more bytes<td>
@ -103,23 +103,23 @@ SIGNATURE_INCLUDED must be set also.
<tr><td>2<td>RESET<td align="center">--<td>
Abnormal close.
SIGNATURE_INCLUDED must be set also.
<tr><td>3<td>SIGNATURE_INCLUDED<td>40 byte <a href="common_structures_spec.html#type_Signature">DSA Signature</a>
<tr><td>3<td>SIGNATURE_INCLUDED<td>40 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Signature">DSA Signature</a>
<td>
Currently sent only with SYNCHRONIZE, CLOSE, and RESET, where it is required.
The signature uses the Destination's <a href="common_structures_spec.html#type_SigningPublicKey">DSA signing keys</a>
The signature uses the Destination's <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPublicKey">DSA signing keys</a>
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.
<tr><td>4<td>SIGNATURE_REQUESTED<td align="center">--<td>
Unused. Requests every packet in the other direction to have SIGNATURE_INCLUDED
<tr><td>5<td>FROM_INCLUDED<td>387+ byte <a href="common_structures_spec.html#struct_Destination">Destination</a>
<tr><td>5<td>FROM_INCLUDED<td>387+ byte <a href="{{ site_url('docs/spec/common-structures') }}#struct_Destination">Destination</a>
<td>
Currently sent only with SYNCHRONIZE, where it is required.
<tr><td>6<td>DELAY_REQUESTED<td>2 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>
<tr><td>6<td>DELAY_REQUESTED<td>2 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>
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.
<tr><td>7<td>MAX_PACKET_SIZE_INCLUDED<td>2 byte <a href="common_structures_spec.html#type_Integer">Integer</a><td>
<tr><td>7<td>MAX_PACKET_SIZE_INCLUDED<td>2 byte <a href="{{ site_url('docs/spec/common-structures') }}#type_Integer">Integer</a><td>
Currently sent with SYNCHRONIZE only.
Was also sent in retransmitted packets until release 0.9.1.
<tr><td>8<td>PROFILE_INTERACTIVE<td align="center">--<td>