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

Tag tweaks and URL fixes for misc/*

Browse Source
This commit is contained in:
str4d
2013-02-01 22:20:09 +00:00
parent 8bdf8ad023
commit c78d3bbb57
13 changed files with 337 additions and 220 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
i2p2www/pages/site/misc/clt.html
View File

@@ -1,11 +1,18 @@
{% extends "global/layout.html" %}
{% block title %}I2P at CLT and PetCon 2009.1{% endblock %}
{% block content %}{% trans -%}<p>
{% block title %}{% trans %}I2P at CLT and PetCon 2009.1{% endtrans %}{% endblock %}
{% block content %}
<p>{% trans -%}
Members of I2P will held a talk at CLT and PetCon 2009.1
Two members of the I2P team will be at two forthcoming Linux day and security convention.<br><br>
On 14th march of 2009 there will be a short talk about general introduction to I2P at the <a href="http://chemnitzer.linux-tage.de/2009/info/">Chemnitz Linux Tag 2009</a> hold by echelon.
Echelon and some other members of the I2P family will attend to the Linux meeting the whole two days (Saturday and Sunday) and will be recognizable as I2P family members. Meet them, ask them your questions, show them your props! Show your support!<br><br>
Just 10 days later the <a href="http://www.pet-con.org/index.php/PET_Convention_2009.1">Privacy and Data Security convention</a> in Dresden will take place.
Two members of the I2P team will be at two forthcoming Linux day and security convention.
{%- endtrans %}</p>
<p>{% trans chemnitzer='http://chemnitzer.linux-tage.de/2009/info/' -%}
On 14th march of 2009 there will be a short talk about general introduction to I2P at the <a href="{{ chemnitzer }}">Chemnitz Linux Tag 2009</a> hold by echelon.
Echelon and some other members of the I2P family will attend to the Linux meeting the whole two days (Saturday and Sunday) and will be recognizable as I2P family members. Meet them, ask them your questions, show them your props! Show your support!
{%- endtrans %}</p>
<p>{% trans petcon='http://www.pet-con.org/index.php/PET_Convention_2009.1' -%}
Just 10 days later the <a href="{{ petcon }}">Privacy and Data Security convention</a> in Dresden will take place.
Again, echelon will attend this event and hold a short talk about general introduction to I2P. Another talk about the profiling by the I2P clients will be held.
{%- endtrans %}</p>

5
i2p2www/pages/site/misc/cvs.html
View File

@@ -1,7 +1,8 @@
{% extends "global/layout.html" %}
{% block title %}CVS{% endblock %}
{% block content %}<p>{% trans -%}
The I2P sourcecode was kept in a CVS repository. Nowadays it is kept in an <a href="{{ site_url('volunteer/develop/monotone') }}">Monotone</a> repository.
{% block content %}
<p>{% trans monotone=site_url('get-involved/guides/monotone') -%}
The I2P sourcecode was kept in a CVS repository. Nowadays it is kept in a <a href="{{ monotone }}">Monotone</a> repository.
For those who aren't very familiar with CVS, there is a
<a href="http://cvsbook.red-bean.com/cvsbook.html">fantastic book</a> on the
subject (developers only need to deal with the first chapter - "An Overview of

34
i2p2www/pages/site/misc/i2ptunnel-migration.html
View File

@@ -1,6 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}i2ptunnel migration{% endblock %}
{% block content %}<h3>{% trans -%}I2PTunnel migration:{%- endtrans %}</h3>
{% block title %}{% trans %}I2PTunnel migration{% endtrans %}{% endblock %}
{% block content %}
<h3>{% trans %}I2PTunnel migration{% endtrans %}</h3>
<p>{% trans -%}
After upgrading to the new architecture, you'll have to do a
@@ -14,19 +15,21 @@ old clientApp configuration, you had:
<p>{% trans -%}To provide that same functionality on the new web architecture:{%- endtrans %}</p>
<ul>
<li>Jump to <a href="http://localhost:7657/i2ptunnel/">http://localhost:7657/i2ptunnel/</a></li>
<li>Click on Add new: [Server tunnel] "GO"</li>
<li>{% trans url='http://localhost:7657/i2ptunnel/' %}Jump to <a href="{{ url }}">{{ url }}</a>{% endtrans %}</li>
<li>{% trans %}Click on Add new: [Server tunnel] "GO"{% endtrans %}</li>
<li><ul>
<li>For the name: <code>"eepsite"</code></li>
<li>For the description: <code>"My eepsite, isn't it pretty?"</code></li>
<li>For the target host: <code>localhost</code></li>
<li>For the target port: <code>80</code></li>
<li>For the private key file: <code>path to "myWebPriv.dat"</code><br />
(it is recommended to copy that .dat to your new install dir)</li>
<li>Check the "Start automatically?" checkbox <code>[X]</code></li>
<li>Click <code>"Save"</code></li>
<li>{% trans %}For the name: <code>"eepsite"</code>{% endtrans %}</li>
<li>{% trans %}For the description: <code>"My eepsite, isn't it pretty?"</code>{% endtrans %}</li>
<li{% trans %}>For the target host:{% endtrans %} <code>localhost</code></li>
<li>{% trans %}For the target port:{% endtrans %} <code>80</code></li>
<li>{% trans -%}
For the private key file: <code>path to "myWebPriv.dat"</code><br />
(it is recommended to copy that .dat to your new install dir)
{%- endtrans %}</li>
<li>{% trans %}Check the "Start automatically?" checkbox{% endtrans %} <code>[X]</code></li>
<li>{% trans %}Click <code>"Save"</code>{% endtrans %}</li>
</ul></li>
<li>It will come back saying:<br />
<li>{% trans %}It will come back saying:{% endtrans %}<br />
<pre>
* Not overwriting existing private keys in /usr/home/jrandom/routers/i2p/myWebPriv.dat
* Ready!
@@ -36,7 +39,7 @@ old clientApp configuration, you had:
<p>{% trans -%}
That's it! Creating a new I2PTunnel server works the same way too, except you
don't need to "copy the old file", obviously. Behind the scenes, it is all driven
by the i2ptunnel.config</code> file, which you may modify externally (if you do,
by the <code>i2ptunnel.config</code> file, which you may modify externally (if you do,
hit "Reload config" on the I2PTunnel web page, which will tear down all of your
existing tunnels and rebuild new ones)
{%- endtrans %}</p>
@@ -47,4 +50,5 @@ into the network before you are able to use the /i2ptunnel/ web
interface. It will say "Please be patient" if you try to
beforehand, which means that it is still trying to build the
necessary I2PTunnel sessions it has been configured to create.
{%- endtrans %}</p>{% endblock %}
{%- endtrans %}</p>
{% endblock %}

268
i2p2www/pages/site/misc/i2ptunnel-services.html
View File

@@ -1,112 +1,180 @@
{% extends "global/layout.html" %}
{% block title %}i2ptunnel services{% endblock %}
{% block content %}{% trans -%}
{% block title %}{% trans %}I2PTunnel services{% endtrans %}{% endblock %}
{% block content %}
<p>{% trans -%}
Below is quick copy of aum's eepsite deployment guide.
{%- endtrans %}<br />
{%- endtrans %}</p>
<br />
<strong>{% trans -%}
1. - Deploy a local server
{%- endtrans %}</strong><ul><li>{% trans %}For simplicity's sake, we will walk through the setup of a web server; however, this procedure is the same regardless what protocol of servers and/or clients you are setting up. {% endtrans %}
<br />
<strong>{% trans %}1. - Deploy a local server{%- endtrans %}</strong>
<ul>
<li>{% trans -%}
For simplicity's sake, we will walk through the setup of a web server; however, this procedure is the same regardless what protocol of servers and/or clients you are setting up.
{%- endtrans %}</li>
<li>{% trans -%}
I recommend the Tiny Httpd web server, thttpd, (windows version available on site) although you can use anything that you feel comfortable with.
{%- endtrans %}</li>
<li>{% trans -%}
Another more robust option would be to use EasyPHP, which is also open source. It comes with PHP, PHPmyadmin, mySQL, and Apache web server. For newbies who have no experience setting up and hosting content over servers, see the hosting page for help.
{%- endtrans %}</li>
<li>{% trans -%}
With the web server you've chosen, configure it to listen on a port of your choice, and serve its documents from a directory of your choice. For this example, we'll assume port 10880.
{%- endtrans %}</li>
<li>{% trans -%}
Make sure your firewall is set up so that you cannot receive incoming connections on this port (which would breach your anonymity).
{%- endtrans %}</li>
<li>{% trans -%}
Test the webserver, by pointing your normal browser (the one with the "direct connection") at <a href="http://localhost:10880" target="_blank">http://localhost:10880</a> (changing the 10880 to the port number you have chosen).
{%- endtrans %}</li>
<li>{% trans -%}
Once your webserver is working, and you can access it locally with your browser, continue to the next step.
{%- endtrans %}</li>
</ul>
<li>{% trans %}I recommend the Tiny Httpd web server , thttpd, (windows version available on site) although you can use anything that you feel comfortable with.{% endtrans %}
<br />
<li>{% trans %}Another more robust option would be to use EasyPHP, which is also open source. It comes with PHP, PHPmyadmin, mySQL, and Apache web server. For newbies who have no experience setting up and hosting content over servers, see the hosting page for help. {% endtrans %}
<br />
<li>{% trans %}With the web server you've chosen, configure it to listen on a port of your choice, and serve its documents from a directory of your choice. For this example, we'll assume port 10880. {% endtrans %}
<br />
<li>{% trans %}Make sure your firewall is set up so that you cannot receive incoming connections on this port (which would breach your anonymity). {% endtrans %}
<br />
<li>{% trans %}Test the webserver, by pointing your normal browser (the one with the "direct connection") at <a href="http://localhost:10880" target="_blank">http://localhost:10880</a> (changing the 10880 to the port number you have chosen). {% endtrans %}
<br />
<li>{% trans %}Once your webserver is working, and you can access it locally with your browser, continue to the next step. {% endtrans %}
<br />
</ul><strong>{% trans %}2 - Generate an I2P Destination Keypair {% endtrans %}</strong><ul><li>{% trans %}I2P does not deal in IP addresses. To protect your anonymity, it deals in unique addresses called destination keys. {% endtrans %}
<strong>{% trans %}2 - Generate an I2P Destination Keypair{% endtrans %}</strong>
<ul>
<li>{% trans -%}
I2P does not deal in IP addresses. To protect your anonymity, it deals in unique addresses called destination keys.
{%- endtrans %}</li>
<li>{% trans -%}
A destination key works a lot like a regular IP address, except that it can't be traced to your IP address or physical location. When users place a request to speak with you, your gateways are the ones that answer for you. So the requesting user can only know the IP address of your gateways. However, gateways don't know your IP address, because gateways are the last nodes on your tunnels, and you anonymously create tunnels by way of garlic routing. (So gateways are like puppets that can't see their masters, and everyone communicates through these puppets)
{%- endtrans %}</li>
<li>{% trans -%}
To deploy a server on I2P, you create a destination keypair. You use the private key to authenticate your server when connecting it to I2P, and you make the public key (aka destination key) known publicly, so others can connect to your server. (indirectly, through your gateways)
{%- endtrans %}</li>
<li>{% trans -%}
Each service you run on I2P requires a different keypair.
{%- endtrans %}</li>
<li>{% trans -%}
To generate your keypair, type the command: <code>java -jar lib/i2ptunnel.jar -nogui -e "genkeys myWebPrivKey.dat myWebPubKey.dat"</code> (all on one line)
{%- endtrans %}</li>
<li>{% trans -%}
In windows, to generate your keypair, type the command: <code>java -jar lib/i2ptunnel.jar -nogui -e "genkeys myWebPrivKey.dat myWebPubKey.dat"</code>
{%- endtrans %}</li>
<li>{% trans -%}
The filenames <code>myWebPrivKey.dat</code> and <code>myWebPubKey.dat</code> are arbitrary - choose whatever you want here, as long as you understand your own choices.
{%- endtrans %}</li>
<li>{% trans -%}
We now need to export your public key into base64 format, which you will share with others.
{%- endtrans %}</li>
<li>{% trans -%}
To convert your myWebPubKey.dat file into shareable base64, type the command <code>java -cp lib/i2p.jar net.i2p.data.Base64 encode myWebPubKey.dat &gt; myWebPubKey.txt</code> (all on one line).
{%- endtrans %}</li>
<li>{% trans -%}
This file you have just generated, <code>myWebPubKey.txt</code>, contains a long base64 string (516 chars at last count), which we call a destination key. All you need to know about this string for now is that it allows remote clients to uniquely pinpoint and connect to your server, just the same way as an IP address allows remote machines to pinpoint and connect to your machine.
{%- endtrans %}</li>
<li>{% trans -%}
However, in contrast to an IP address, there is no way to trace your machine's physical location - even though your server can be addressed via I2P, your IP address cannot be traced or associated with this destination key.
{%- endtrans %}</li>
</ul>
<br />
<li>{% trans %}A destination key works a lot like a regular IP address, except that it can't be traced to your IP address or physical location. When users place a request to speak with you, your gateways are the ones that answer for you. So the requesting user can only know the IP address of your gateways. However, gateways don't know your IP address, because gateways are the last nodes on your tunnels, and you anonymously create tunnels by way of garlic routing. (So gateways are like puppets that can't see their masters, and everyone communicates through these puppets) {% endtrans %}
<br />
<li>{% trans %}To deploy a server on I2P, you create a destination keypair. You use the private key to authenticate your server when connecting it to I2P, and you make the public key (aka destination key) known publicly, so others can connect to your server. (indirectly, through your gateways) {% endtrans %}
<br />
<li>{% trans %}Each service you run on I2P requires a different keypair. {% endtrans %}
<br />
<li>{% trans %}To generate your keypair, type the command: java -jar lib/i2ptunnel.jar -nogui -e "genkeys myWebPrivKey.dat myWebPubKey.dat" (all on one line) {% endtrans %}
<br />
<li>{% trans %}In windows, to generate your keypair, type the command: java -jar lib/i2ptunnel.jar -nogui -e "genkeys myWebPrivKey.dat myWebPubKey.dat" {% endtrans %}
<br />
<li>{% trans %}The filenames myWebPrivKey.dat and myWebPubKey.dat are arbitrary - choose whatever you want here, as long as you understand your own choices. {% endtrans %}
<br />
<li>{% trans %} We now need to export your public key into base64 format, which you will share with others. {% endtrans %}
<br />
<li>{% trans %}To convert your myWebPubKey.dat file into shareable base64, type the command java -cp lib/i2p.jar net.i2p.data.Base64 encode myWebPubKey.dat &gt; myWebPubKey.txt (all on one line). {% endtrans %}
<strong>{% trans %}3 - Open a 'Tunnel' from I2P To Your Server{% endtrans %}</strong>
<ul>
<li>{% trans -%}
For clients elsewhere in I2P to be able to access your server, you must run a 'bridge' or 'tunnel', which takes connections from these clients and forwards them to your local server.
{%- endtrans %}</li>
<li>{% trans -%}
To activate such a tunnel, type the command <code>java -jar lib/i2ptunnel.jar -nogui -e "server localhost 10880 myWebPrivKey.dat"</code> (all one line).
{%- endtrans %}</li>
<li>{% trans -%}
If you used different filenames or port number earlier on, change these accordingly
{%- endtrans %}</li>
<li>{% trans -%}
Windows users, remember to replace apostrophes with double quotes. Thus: <code>java -jar lib/i2ptunnel.jar -nogui -e "server localhost 10880 myWebPrivKey.dat"</code>
{%- endtrans %}</li>
<li>{% trans -%}
Within a few seconds, the 'tunnel' should now be active, and remote clients should be able to reach your server anonymously. Remember to let your router "warm up" before opening clients to it.
{%- endtrans %}</li>
</ul>
<br />
<li>{% trans %}This file you have just generated, myWebPubKey.txt, contains a long base64 string (516 chars at last count), which we call a destination key. All you need to know about this string for now is that it allows remote clients to uniquely pinpoint and connect to your server, just the same way as an IP address allows remote machines to pinpoint and connect to your machine. {% endtrans %}
<br />
<li>{% trans %}However, in contrast to an IP address, there is no way to trace your machine's physical location - even though your server can be addressed via I2P, your IP address cannot be traced or associated with this destination key. {% endtrans %}
<br />
</ul><strong>{% trans %}3 - Open a 'Tunnel' from I2P To Your Server{% endtrans %}</strong><ul><li>{% trans %}For clients elsewhere in I2P to be able to access your server, you must run a 'bridge' or 'tunnel', which takes connections from these clients and forwards them to your local server {% endtrans %}
<br />
<li>{% trans %}To activate such a tunnel, type the command java -jar lib/i2ptunnel.jar -nogui -e "server localhost 10880 myWebPrivKey.dat" (all one line) {% endtrans %}
<br />
<li>{% trans %}If you used different filenames or port number earlier on, change these accordingly {% endtrans %}
<br />
<li>{% trans %}Windows users, remember to replace apostrophes with double quotes. Thus: java -jar lib/i2ptunnel.jar -nogui -e "server localhost 10880 myWebPrivKey.dat" {% endtrans %}
<br />
<li>{% trans %}Within a few seconds, the 'tunnel' should now be active, and remote clients should be able to reach your server anonymously. Remember to let your router "warm up" before opening clients to it. {% endtrans %}
<br />
</ul><strong>{% trans %}4 - Update Your hosts.txt File {% endtrans %}</strong><ul><li>{% trans %}To test your own server locally, you'll need to create an entry in your hosts.txt file, so I2P can translate the simple URL you place in the browser's address bar into the full public key text needed to find your server. {% endtrans %}
<strong>{% trans %}4 - Update Your hosts.txt File {% endtrans %}</strong>
<ul>
<li>{% trans -%}
To test your own server locally, you'll need to create an entry in your hosts.txt file, so I2P can translate the simple URL you place in the browser's address bar into the full public key text needed to find your server.
{%- endtrans %}</li>
<li>{% trans -%}
Edit your hosts.txt, and add the line myserver.i2p=blahblahblah, where myserver.i2p is an I2P 'domain' you want to associate with your site, and the blahblahblah is the text of the base64 public key you created earlier in the file myWebPubKey.txt
{%- endtrans %}</li>
<li>{% trans -%}
With this in place, you and others can reach your server with the simple domain name myserver.i2p in the browser's address bar.
{%- endtrans %}</li>
</ul>
<br />
<li>{% trans %}Edit your hosts.txt, and add the line myserver.i2p=blahblahblah, where myserver.i2p is an I2P 'domain' you want to associate with your site, and the blahblahblah is the text of the base64 public key you created earlier in the file myWebPubKey.txt {% endtrans %}
<br />
<li>{% trans %}With this in place, you and others can reach your server with the simple domain name myserver.i2p in the browser's address bar. {% endtrans %}
<br />
</ul><strong>{% trans %}5 - Surf Your Site Within I2P{% endtrans %}</strong><ul><li>{% trans %}Using your secondary browser - the one you earlier configured to use localhost:4444 as a proxy - point this browser to the address <a href="http://myserver.i2p" target="_blank">http://myserver.i2p{% endtrans %}</a>
<br />
<li>{% trans %}You should see the main page of your webserver come up. {% endtrans %}
<br />
</ul><strong>{% trans %}6 - Create a Local Client Tunnel Connection {% endtrans %}</strong><ul><li>{% trans %}We now have to think beyond just web servers. {% endtrans %}
<br />
<li>{% trans %}As you grow into I2P and get more of a 'feel' for it, you will want to use all manner of servers and clients. {% endtrans %}
<br />
<strong>{% trans %}5 - Surf Your Site Within I2P{% endtrans %}</strong>
<ul>
<li>{% trans -%}
Using your secondary browser - the one you earlier configured to use localhost:4444 as a proxy - point this browser to the address <a href="http://myserver.i2p" target="_blank">http://myserver.i2p</a>
{%- endtrans %}</li>
<li>{% trans -%}
You should see the main page of your webserver come up.
{%- endtrans %}</li>
</ul>
<li>{% trans %}The beauty of I2P is that it allows standard Internet clients and servers for most protocols to be transparently 'tunneled' through the anonymous network. {% endtrans %}
<br />
<li>{% trans %}You can run mailservers/clients, nameservers/clients, newsservers/clients - almost anything at all - perhaps even FTP in passive mode. {% endtrans %}
<br />
<li>{% trans %}Now, we'll create a client tunnel. This is like the server tunnel we created earlier, but works in reverse. It listens to a port on your local machine; your local client connects to this port; the connection gets forwarded through I2P to the service on the other end. {% endtrans %}
<br />
<li>{% trans %}To open your client tunnel for your server, type the command java -jar lib/i2ptunnel.jar -nogui -e "config localhost 7654" -e "client 10888 textofbase64key" (all one line). {% endtrans %}
<br />
<li>{% trans %}The port 10888 is arbitrary - it just needs to be something other than the physical port your server is listening on. {% endtrans %}
<br />
<li>{% trans %}textofbase64key is simply the contents of the public key text file myWebPubKey.txt, reproduced fully on one line (alternately, instead of textofbase64key, you can specify the name from your hosts.txt - e.g. myserver.i2p) {% endtrans %}
<br />
<li>{% trans %}Within a minute or two of launching this command, the client tunnel from your local machine into I2P will be open and ready for use. {% endtrans %}
<br />
<li>{% trans %}Point your regular web browser (ie, not the one you configured to use localhost:4444), and point it to <a href="http://localhost:10888" target="_blank">http://localhost:10888</a> {% endtrans %}
<strong>{% trans %}6 - Create a Local Client Tunnel Connection {% endtrans %}</strong>
<ul>
<li>{% trans -%}
We now have to think beyond just web servers.
{%- endtrans %}</li>
<li>{% trans -%}
As you grow into I2P and get more of a 'feel' for it, you will want to use all manner of servers and clients.
{%- endtrans %}</li>
<li>{% trans -%}
The beauty of I2P is that it allows standard Internet clients and servers for most protocols to be transparently 'tunneled' through the anonymous network.
{%- endtrans %}</li>
<li>{% trans -%}
You can run mailservers/clients, nameservers/clients, newsservers/clients - almost anything at all - perhaps even FTP in passive mode.
{%- endtrans %}</li>
<li>{% trans -%}
Now, we'll create a client tunnel. This is like the server tunnel we created earlier, but works in reverse. It listens to a port on your local machine; your local client connects to this port; the connection gets forwarded through I2P to the service on the other end.
{%- endtrans %}</li>
<li>{% trans -%}
To open your client tunnel for your server, type the command <code>java -jar lib/i2ptunnel.jar -nogui -e "config localhost 7654" -e "client 10888 textofbase64key"</code> (all one line).
{%- endtrans %}</li>
<li>{% trans -%}
The port 10888 is arbitrary - it just needs to be something other than the physical port your server is listening on.
{%- endtrans %}</li>
<li>{% trans -%}
textofbase64key is simply the contents of the public key text file myWebPubKey.txt, reproduced fully on one line (alternately, instead of textofbase64key, you can specify the name from your hosts.txt - e.g. myserver.i2p)
{%- endtrans %}</li>
<li>{% trans -%}
Within a minute or two of launching this command, the client tunnel from your local machine into I2P will be open and ready for use.
{%- endtrans %}</li>
<li>{% trans -%}
Point your regular web browser (ie, not the one you configured to use localhost:4444), and point it to <a href="http://localhost:10888" target="_blank">http://localhost:10888</a>
{%- endtrans %}</li>
<li>{% trans -%}
Verify that the main page of your server eventually comes up in your browser.
{%- endtrans %}</li>
<li>{% trans -%}
You use the same procedure for using any local client program to access a remote I2P server - just get the base64 public key (called destination key) of the remote server, choose a local port to connect to the remote server, open the tunnel, and just connect with your client to your heart's content.
{%- endtrans %}</li>
</ul>
<br />
<li>{% trans %}Verify that the main page of your server eventually comes up in your browser. {% endtrans %}
<br />
<li>{% trans %}You use the same procedure for using any local client program to access a remote I2P server - just get the base64 public key (called destination key) of the remote server, choose a local port to connect to the remote server, open the tunnel, and just connect with your client to your heart's content. {% endtrans %}
<br />
</ul><strong>{% trans %}7 - Share your server details with others{% endtrans %}</strong><ul><li>{% trans %}Using an anonymous medium (eg the one of the I2P IRC servers or ugha's wiki), post your domain name (eg <a href="http://www.mynick.i2p" target="_blank">www.mynick.i2p</a> as well as your destination key. Others will then be able to reach your server remotely, without either of you jeopardizing your anonymity. {% endtrans %}
<br />
<li>{% trans %}Remember, you can go to What's on I2P and find the latest public keys linked to their URL. You should also post your own public key and URL their. However, you will want to do this anonymously, of course. Drupal.i2p.net is currently, as of this writing, only accessible from the net. So, to access the outside WWW anonymously from inside of I2P, you will need to start up your script called startSquid. Do it the same way you have been doing these other scripts. Reconfigure your browser to proxy on localhost:5555, as defined in the script, and when the script has generated it's keys, you can access the squid proxy. Put any WWW URL (such as Google or this i2p site) into your browser's address bar and you will be surfing the World Wide Web anonymously. Now you can safely post your public key, and no one can detect your IP address. {% endtrans %}
<br />
</ul><strong>{% trans %}8 - Write Some Scripts To Handle All This Menial Nonsense{% endtrans %}</strong><ul><li>{% trans %}It would drive most people crazy, going through all these steps every time one sets up an I2P server, and/or deploys a client. {% endtrans %}
<br />
<li>{% trans %}Aum's website <a href="http://www.freenet.org.nz/i2p/" target="_blank">http://www.freenet.org.nz/i2p/</a> has a script called setupServer.py which automates all this nonsense into one simple command line . But I respect that people's tastes in user interfaces differ, and trying to write something which satisfies everyone's needs usually results in something so complex that it turns into newbie-repellent. {% endtrans %}
<strong>{% trans %}7 - Share your server details with others{% endtrans %}</strong>
<ul>
<li>{% trans -%}
Using an anonymous medium (eg the one of the I2P IRC servers or ugha's wiki), post your domain name (eg <a href="http://www.mynick.i2p" target="_blank">www.mynick.i2p</a> as well as your destination key. Others will then be able to reach your server remotely, without either of you jeopardizing your anonymity.
{%- endtrans %}</li>
<li>{% trans -%}
Remember, you can go to What's on I2P and find the latest public keys linked to their URL. You should also post your own public key and URL their. However, you will want to do this anonymously, of course. Drupal.i2p.net is currently, as of this writing, only accessible from the net. So, to access the outside WWW anonymously from inside of I2P, you will need to start up your script called startSquid. Do it the same way you have been doing these other scripts. Reconfigure your browser to proxy on localhost:5555, as defined in the script, and when the script has generated it's keys, you can access the squid proxy. Put any WWW URL (such as Google or this i2p site) into your browser's address bar and you will be surfing the World Wide Web anonymously. Now you can safely post your public key, and no one can detect your IP address.
{%- endtrans %}</li>
</ul>
<br />
<li>{% trans %}So please feel free to use and/or customize setupServer.py to taste, or write your own in Python or another language. {% endtrans %}
<br />
<li>{% trans %}Also, you may want to write a script which handles the startup of the I2P Router, the eepProxy, plus any and all tunnels you are using. I've got such a script called startEverything.sh, which gets launched at system startup. (Be sure to search this site for template scripts to automate your I2P commands. If I create a page for one, I'll try to remember to link it here. {% endtrans %}
<br />
<li>{% trans %}Exercise for Windows users - port setupServer.py into a MS-DOS .BAT file. { %endtrans % }
<br />
<strong>{% trans %}8 - Write Some Scripts To Handle All This Menial Nonsense{% endtrans %}</strong>
<ul>
<li>{% trans -%}
It would drive most people crazy, going through all these steps every time one sets up an I2P server, and/or deploys a client.
{%- endtrans %}</li>
<li>{% trans -%}
Aum's website <a href="http://www.freenet.org.nz/i2p/" target="_blank">http://www.freenet.org.nz/i2p/</a> has a script called setupServer.py which automates all this nonsense into one simple command line . But I respect that people's tastes in user interfaces differ, and trying to write something which satisfies everyone's needs usually results in something so complex that it turns into newbie-repellent.
{%- endtrans %}</li>
<li>{% trans -%}
So please feel free to use and/or customize setupServer.py to taste, or write your own in Python or another language.
{%- endtrans %}</li>
<li>{% trans -%}
Also, you may want to write a script which handles the startup of the I2P Router, the eepProxy, plus any and all tunnels you are using. I've got such a script called startEverything.sh, which gets launched at system startup. (Be sure to search this site for template scripts to automate your I2P commands. If I create a page for one, I'll try to remember to link it here.
{%- endtrans %}</li>
<li>{% trans -%}
Exercise for Windows users - port setupServer.py into a MS-DOS .BAT file.
{%- endtrans %}</li>
</ul>
{% endblock %}

6
i2p2www/pages/site/misc/invisiblenet.html
View File

@@ -1,14 +1,14 @@
{% extends "global/layout.html" %}
{% block title %}Old Documents{% endblock %}
{% block title %}{% trans %}Old Documents{% endtrans %}{% endblock %}
{% block content %}
{% trans -%}
<p>{% trans -%}
Following is a list of documents originally on www.invisiblenet.net/i2p/ and
rescued via the
<a href="http://www.archive.org/">Wayback Machine</a>.
They are quite dated and may or may not be accurate.
However, the I2CP and I2NP documents in particular have some good information.
{%- endtrans %}
{%- endtrans %}</p>
<H3>Index of /i2p</H3>
<PRE>Name Last modified Size

40
i2p2www/pages/site/misc/jbigi.html
View File

@@ -1,6 +1,6 @@
{% extends "global/layout.html" %}
{% block title %}jbigi{% endblock %}
{% block lastupdated %}August 2011{% endblock %}
{% block lastupdated %}{% trans %}August 2011{% endtrans %}{% endblock %}
{% block accuratefor %}0.8.7{% endblock %}
{% block content %}
<h2>{% trans %}Overview{% endtrans %}</h2>
@@ -10,24 +10,27 @@ manual work and a piece of chewing gum we have made several
cryptography operations quite a bit faster.
{%- endtrans %}</p>
<p>{% trans -%}
<p>{% trans gmplib='http://gmplib.org/',
func='http://gmplib.org/manual-4.3.2/Integer-Exponentiation.html#Integer-Exponentiation',
bigint='http://download.oracle.com/javase/1.5.0/docs/api/java/math/BigInteger.html#modPow%28java.math.BigInteger,%20java.math.BigInteger%29' -%}
The speedup comes from the super-fast
<a href="http://gmplib.org/">GNU MP Bignum library (libgmp)</a>.
<a href="{{ gmplib }}">GNU MP Bignum library (libgmp)</a>.
We use a single function from libgmp -
<a href="http://gmplib.org/manual-4.3.2/Integer-Exponentiation.html#Integer-Exponentiation">mpz_powm()</a>
<a href="{{ func }}">mpz_powm()</a>
as a replacement for the
<a href="http://download.oracle.com/javase/1.5.0/docs/api/java/math/BigInteger.html#modPow%28java.math.BigInteger,%20java.math.BigInteger%29">Java Math library's BigInteger modPow()</a>.
<a href="{{ bigint }}">Java Math library's BigInteger modPow()</a>.
As modPow() is a significant computational portion of many crypto operations, this is of significant benefit.
{%- endtrans %}</p>
<p>{% trans -%}
<p>{% trans nativebigint='http://docs.i2p-projekt.de/javadoc/net/i2p/util/NativeBigInteger.html',
bigint='http://download.oracle.com/javase/1.5.0/docs/api/java/math/BigInteger.html#modPow%28java.math.BigInteger,%20java.math.BigInteger%29' -%}
The standard I2P installation includes about 20 versions of the library for different platforms,
each about 50KB, inside the jbigi.jar file.
The initialization of the JBigI library, including CPU identification, selection, and extraction
of the correct loadable module, is handled by the
<a href="http://docs.i2p-projekt.de/javadoc/net/i2p/util/NativeBigInteger.html">NativeBigInteger class</a>.
<a href="{{ nativebigint }}">NativeBigInteger class</a>.
If no module is available for the current platform, the standard
<a href="http://download.oracle.com/javase/1.5.0/docs/api/java/math/BigInteger.html#modPow%28java.math.BigInteger,%20java.math.BigInteger%29">Java Math library's BigInteger modPow()</a>
<a href="{{ bigint }}">Java Math library's BigInteger modPow()</a>
is used.
{%- endtrans %}</p>
@@ -81,12 +84,12 @@ The network average for encrypt time is about 20ms.
If your encrypt time is less than 50ms for a relatively new processor, or less than 100ms
for an older processor, and the native BigInteger library was loaded, you are probably fine.
{%- endtrans %}</li>
<li>{% trans -%}
<li>{% trans downloads=get_url('downloads_list') -%}
Get the latest released source code of I2P from
<a href="{{ url_for('downloads_list', lang=g.lang) }}">the download page</a>, or get the cutting-edge source
<a href="{{ downloads }}">the download page</a>, or get the cutting-edge source
out of the monotone database mtn.i2p2.de
{%- endtrans %}</li>
<li>{$ trans %}Inside the source tree change directory to: <code>core/c/jbigi</code>{% endtrans %}</li>
<li>{% trans %}Inside the source tree change directory to: <code>core/c/jbigi</code>{% endtrans %}</li>
<li>{% trans -%}
Read the README file.
If you have a /usr/lib/libgmp.so file, you do not have to download GMP.
@@ -102,7 +105,7 @@ Otherwise change the settings. Remember, you need the Java SDK installed.
{%- endtrans %}</li>
<li>{% trans -%}
Run <code>build.sh</code> (if you downloaded GMP) or
<code>build.sh dynamic</code> (if you have /usr/lib/libgmp.so).<br/>
<code>build.sh dynamic</code> (if you have /usr/lib/libgmp.so).<br/>
Maybe the build spewed out some errors of missing jni.h and jni_md.h files.
Either copy these files from your java install into the core/c/jbigi/jbigi/include/ directory,
or fix $JAVA_HOME.<br>
@@ -122,16 +125,13 @@ native run time: 5842ms ( 57ms each)
java run time: 41072ms (406ms each)
native = 14.223802103622907% of pure java time
</pre>
{% trans %}If the native is indeed 5-7x faster (or more) then it looks all good. If not, please
report.{% endtrans %}</li>
{% trans %}If the native is indeed 5-7x faster (or more) then it looks all good. If not, please report.{% endtrans %}</li>
<li>{% trans %}Copy <code>libjbigi.so</code> to your i2p directory{% endtrans %}</li>
<li>{% trans %}Restart your I2P programs.{% endtrans %}</li>
<li>{% trans %}On{% endtrans %}
{% trans %}<a href="http://localhost:7657/stats.jsp">http://localhost:7657/stats.jsp</a>
<li>{% trans -%}
On <a href="http://localhost:7657/stats.jsp">http://localhost:7657/stats.jsp</a>
the <code>crypto.elGamal.decrypt</code> and <code>crypto.elGamal.encrypt</code>
should be a lot faster.</li>{% endtrans %}
should be a lot faster.
{%- endtrans %}</li>
</ol>
{% endblock %}

16
i2p2www/pages/site/misc/jrandom-awol.html
View File

@@ -1,20 +1,24 @@
{% extends "global/layout.html" %}
{% block title %}Jrandom's Announcement{% endblock %}
{% block title %}{% trans %}Jrandom's Announcement{% endtrans %}{% endblock %}
{% block content %}
{% trans %}The following message was received in mid-November 2007. We have no further information
on jrandom's status.{% endtrans %}
<p>{% trans -%}
The following message was received in mid-November 2007. We have no further information
on jrandom's status.
{%- endtrans %}</p>
<p>{% trans site=site_url() -%}
Subsequently, in an unrelated incident, the hosting company for
all *.i2p.net servers (except forum.i2p.net) suffered a power outage
on January 13, 2008, and the i2p.net servers did not fully return to service.
As only jrandom has the credentials required to restore service,
and he could not be contacted,
we moved all public services to <a href="http://www.i2p2.de/">www.i2p2.de</a>
we moved all public services to <a href="{{ site }}">www.i2p2.de</a>
and related subdomains.
{%- endtrans %}</p>
<p>{% trans -%}
<p>{% trans forum=i2pconv('forum.i2p') -%}
Approximately two months later, for unrelated reasons,
forum.i2p.net was moved to <a href="http://forum.i2p2.de/">forum.i2p2.de</a>.
forum.i2p.net was moved to <a href="http://{{ forum }}/">{{ forum }}</a>.
{%- endtrans %}</p>
<pre>
-----BEGIN PGP SIGNED MESSAGE-----

57
i2p2www/pages/site/misc/manual-wrapper.html
View File

@@ -1,55 +1,68 @@
{% extends "global/layout.html" %}
{% block title %}Manually Installing the Java Wrapper{% endblock %}
{% block title %}{% trans %}Manually Installing the Java Wrapper{% endtrans %}{% endblock %}
{% block content %}
<h1>{% trans %}Manually Installing the Java Wrapper{% endtrans %}</h1>
<p>{% trans -%}
The installation package for the <a href="{{ url_for('downloads_list', lang=g.lang) }}">I2P router</a> comes
<p>{% trans downloads=get_url('downloads_list') -%}
The installation package for the <a href="{{ downloads }}">I2P router</a> comes
with a Java wrapper for the most common architectures. If your system is not
supported by our installer&mdash;or if you want to update the wrapper to a
newer version&mdash;the following steps describe installing the wrapper manually.
{%- endtrans %}</p>
<ul>
<li>{% trans %}Check Tanuki Software's <a href="http://wrapper.tanukisoftware.com/doc/english/download.jsp#stable">download page</a>
for your platform. Is your platform listed? If so, you're in
luck! Download the most recent version of the Community Edition for your OS and
CPU and move to <a href="#packaged">the next step</a>{% endtrans %}</li>
<li>{% trans %}If your platform does not have an already compiled wrapper available, you
may be able to compile it yourself. If you are willing to have a go at it, move
on to <a href="#compiling">compiling</a> the wrapper for your system.{% endtrans %}</li>
<li>{% trans -%}
Check Tanuki Software's <a href="http://wrapper.tanukisoftware.com/doc/english/download.jsp#stable">download page</a>
for your platform. Is your platform listed? If so, you're in
luck! Download the most recent version of the Community Edition for your OS and
CPU and move to <a href="#packaged">the next step</a>.
{%- endtrans %}</li>
<li>{% trans -%}
If your platform does not have an already compiled wrapper available, you
may be able to compile it yourself. If you are willing to have a go at it, move
on to <a href="#compiling">compiling</a> the wrapper for your system.
{%- endtrans %}</li>
</ul>
<h2 id="packaged">{% trans %}Using existing binaries{% endtrans %}</h2>
{% trans %}In the steps below, $I2P means <em>the location I2P was installed to</em>.{% endtrans %}
<p>{% trans -%}
In the steps below, $I2P means <em>the location I2P was installed to</em>.
{%- endtrans %}</p>
<ol>
<li><code>tar xzf wrapper-*.tar.gz</code></li>
<li><code>cp wrapper*/bin/wrapper $I2P/i2psvc</code></li>
<li><code>cp wrapper*/lib/wrapper.jar $I2P/lib</code></li>
<li><code>cp wrapper*/lib/libwrapper.so $I2P/lib</code></li>
<li>{% trans %}Try to start I2P using {% endtrans %}<code>$I2P/i2prouter start</code></li>
<li><code>tail -f /tmp/wrapper.log</code> and look for any problems.</li></ol>
{% trans %}If this did not work you'll need to use <code>runplain.sh</code> to start I2P.{% endtrans %}
<li>{% trans %}Try to start I2P using <code>$I2P/i2prouter start</code>{% endtrans %}</li>
<li>{% trans %}<code>tail -f /tmp/wrapper.log</code> and look for any problems.{% endtrans %}</li>
</ol>
<p>{% trans -%}
If this did not work you'll need to use <code>runplain.sh</code> to start I2P.
{%- endtrans %}</p>
<h2 id="compiling">{% trans %}Compiling from source{% endtrans %}</h2>
{% trans %}These steps worked to compile the wrapper for use on a mipsel system running Debian. The steps <strong>will</strong> need to be altered for your system.{% endtrans %}
<p>{% trans -%}
These steps worked to compile the wrapper for use on a mipsel system running Debian. The steps <strong>will</strong> need to be altered for your system.
{%- endtrans %}</p>
<ol>
<li>{% trans %}Download the source archive for the community version of the wrapper from <a href="http://wrapper.tanukisoftware.com/downloads">wrapper download page</a>.{% endtrans %}</li>
<li>{% trans %}Extract the tarball{% endtrans %}<br />
&nbsp;&nbsp;&nbsp;&nbsp;<code>tar xzf wrapper_3.5.13_src.tar.gz</code></li>
<li>Set environment variables ANT_HOME and JAVA_HOME. In Debian, one can<br />
<li>{% trans %}Set environment variables <code>ANT_HOME</code> and <code>JAVA_HOME</code>. For example, in Debian:{% endtrans %}<br />
&nbsp;&nbsp;&nbsp;&nbsp;<code>export ANT_HOME=/usr/share/ant</code><br />
&nbsp;&nbsp;&nbsp;&nbsp;<code>export JAVA_HOME=/usr/lib/jvm/default-java</code></li>
<li>Since there isn't a Makefile for Mipsel, we'll make a copy of an already existing makefile<br />
<li>{% trans %}Since there isn't a Makefile for Mipsel, we'll make a copy of an already existing makefile:{% endtrans %}<br />
&nbsp;&nbsp;&nbsp;&nbsp;<code>cp src/c/Makefile-linux-x86-32.make src/c/Makefile-linux-mipsel-32.make</code></li>
<li>Now we can attempt to compile the wrapper<br />
&nbsp;&nbsp;&nbsp;&nbsp;<code>./build32.sh</code> (use <code>./build64.sh</code> if you have a 64bit CPU and JVM)</li>
<li>Copy the wrapper into its proper place:
<li>{% trans %}Now we can attempt to compile the wrapper:{% endtrans %}<br />
&nbsp;&nbsp;&nbsp;&nbsp;<code>./build32.sh</code> ({% trans %}use <code>./build64.sh</code> if you have a 64bit CPU and JVM{% endtrans %})</li>
<li>{% trans %}Copy the wrapper into its proper place:{% endtrans %}
<ul>
<li><code>cp bin/wrapper $I2P/i2psvc</code></li>
<li><code>cp lib/wrapper.jar $I2P/lib</code></li>
<li><code>cp lib/libwrapper.so $I2P/lib</code></li>
</ul></li>
<li>{% trans %}Try to start I2P using <code>$I2P/i2prouter start</code>{% endtrans %}</li>
<li><code>tail -f /tmp/wrapper.log</code> and look for any problems.</li>
<li>{% trans %}<code>tail -f /tmp/wrapper.log</code> and look for any problems.{% endtrans %}</li>
</ol>
{% trans %}If this did not work you'll need to use <code>runplain.sh</code> to start I2P.{% endtrans %}
<p>{% trans %}If this did not work you'll need to use <code>runplain.sh</code> to start I2P.{% endtrans %}</p>
{% endblock %}

14
i2p2www/pages/site/misc/minwww.html
View File

@@ -1,9 +1,10 @@
{% extends "global/layout.html" %}
{% block title %}minwww{% endblock %}
{% block content %}<p>{% trans -%}
Here's an outline and rationale for a minimal WWW proxy app for use over
I2P.
{% block content %}
<p>{% trans -%}
Here's an outline and rationale for a minimal WWW proxy app for use over I2P.
{%- endtrans %}</p>
<p>{% trans -%}
HTTP operation over I2P using I2PTunnel. When the base SocketLibrary
is out, the only significant difference will be the 'wrapRequest' and
@@ -42,6 +43,7 @@ skipped)
26: receiveACK receiveClose
27: sentSuccess
</pre>
<p>{% trans -%}
An optimized form, designed to handle only 128KB [1] files and pages, can
operate significantly faster:
@@ -65,6 +67,7 @@ operate significantly faster:
15: closeCon
16: closed
</pre>
<p>{% trans -%}
The difference in network load and latency is significant - this is
essentially a UDP version of HTTP. On the normal web, we can't really do that,
@@ -76,6 +79,7 @@ DataMessage with a DeliveryStatusMessage to provide guaranteed delivery), the
MinWWW proxy deals with resends (if necessary - in I2PTunnel today, there are no
resends).
{%- endtrans %}</p>
<p>{% trans -%}
The data that the MinWWW proxy and server need to wrap is trivial - when the
proxy wants to send "GET /", it prepends it with the I2P Destination sending
@@ -85,6 +89,7 @@ response, and sends a reply to the MinWWW proxy containing the response,
prefixed with the original request ID. That response is taken and passed back
to the browser and the connection is closed.
{%- endtrans %}</p>
<p>{% trans -%}
In addition, the MinWWW proxy can choose the MinWWW server to use from a
list, going through some round robin or other algorithm, so that there are
@@ -92,6 +97,7 @@ multiple outproxies merged transparently. The bandwidth required for running
one of these outproxies is also greatly reduced, since it will only handle 128KB
files (aka no one is going to be downloading porn, warez, etc).
{%- endtrans %}</p>
<p>{% trans -%}
The functionality /is/ limited, but 128KB of data is a lot for a single HTTP
request or response. The above diagrams are also unrealistic in their hops -
@@ -103,6 +109,7 @@ entire tunnel path (4+ remote hops each time when tunnels are 2 remote hops
in each stretch), leaving MinWWW with only two full traversals (one for the
request, one for the response), instead of 10.
{%- endtrans %}</p>
<p>{% trans -%}
Implementing the MinWWW proxy and server should be fairly easy - read an HTTP
request from the client fully (perhaps only start out with HTTP GET, leaving
@@ -111,6 +118,7 @@ in turn simply needs to parse the request to either open a socket or URL,
send the request, wait for the response, and send it back through the network.
If someone were to implement this, it would be Good :)
{%- endtrans %}</p>
<p>{% trans -%}
[1] Why 128KB files? Currently I2CP allows functionally arbitrary message
size, but that's going to be going away since it involves either excessive memory

12
i2p2www/pages/site/misc/myi2p.html
View File

@@ -1,16 +1,18 @@
{% extends "global/layout.html" %}
{% block title %}MYI2P{% endblock %}
{% block content %}<p>{% trans -%}
{% block content %}
<p>{% trans -%}
There has been discussion about a distributed blogging application for a few
months now called "MyI2P". While the original discussions were lost, we were
able to retrieve a Google <a href="http://dev.i2p.net/~jrandom/i2p.net/myi2p.html">cache</a>
of it. It isn't pretty, but it includes the basic overview and some discussion
that ensued.{%- endtrans %}</p>
that ensued.
{%- endtrans %}</p>
<p>{% trans -%}
<p>{% trans roadmap=site_url('get-involved/roadmap'), datagrams=site_url('docs/spec/datagrams') -%}
The application itself is not yet implemented, and the ideas behind it have
been made less ambitious over time, but they are still valid and the current
<a href="{{ site_url('volunteer/roadmap') }}">plan</a> is to have the core MyI2P functionality available
<a href="{{ roadmap }}">plan</a> is to have the core MyI2P functionality available
along side the I2P 1.0 release. That will include a distributed address book
to enable secure, distributed, and human readable naming by sacrificing the
need for global uniqueness - basically everyone has their own local address book
@@ -21,7 +23,7 @@ system using a reduced and secured subset of
<a href="http://www.phpbb.com/phpBB/faq.php?mode=bbcode">bbcode</a> to essentially
provide an anonymous <a href="http://www.livejournal.com/">LiveJournal</a> with
a 'friends list' and transparent access control (authenticated by the I2P
<a href="{{ site_url{'docs/spec/datagrams') }}">datagrams</a> with rules defined based on the address book).
<a href="{{ datagrams }}">datagrams</a> with rules defined based on the address book).
{%- endtrans %}</p>
<p>{% trans -%}

12
i2p2www/pages/site/misc/ratestats.html
View File

@@ -1,15 +1,15 @@
{% extends "global/layout.html" %}
{% block title %}RateStat list{% endblock %}
{% block title %}{% trans %}RateStat list{% endtrans %}{% endblock %}
{% block accuratefor %}0.8.7{% endblock %}
{% block content %}
<h1>{% trans %}RateStat list{% endtrans %}</h1>
<p>{% trans %}I2P enables the collection of a wide range of rates, the list published here is accurate as of I2P version 0.8.7.{% endtrans %}</p>
<p>{% trans %}The list was gathered using the following command in the top directory of the branch i2p.i2p,
<p>{% trans %}I2P enables the collection of a wide range of rates.{% endtrans %}</p>
<p>{% trans %}The list was gathered using the following command in the top directory of the branch i2p.i2p:{% endtrans %}</p>
<pre> find . -name '*' -print | xargs --max-args=3 grep -n --color=auto addRateData | awk 'match($0, /addRateData\(\"(.*)\"/, a) {print a[1]}' | awk '!_[$0]++' | sort > rates.txt
</pre>
All options aren't needed, but it works.{% endtrans %}
</p>
<p>{% trans %}All options aren't needed, but it works.{% endtrans %}</p>
<h2>{% trans %}RateStats{% endtrans %}</h2>
<h2>RateStats</h2>
<div class="box" style="clear: none;"><pre>
bwLimiter.inboundDelayedTime
bwLimiter.outboundDelayedTime

9
i2p2www/pages/site/misc/transition-guide.html
View File

@@ -1,15 +1,16 @@
{% extends "global/layout.html" %}
{% block title %}Monotone{% endblock %}
{% block content %}<p>{% trans -%}
{% block content %}
<p>{% trans forum=i2pconv('forum.i2p'), newdevs=site_url('get-involved/guides/new-developers') -%}
The I2P sourcecode is kept in several distributed monotone repositories.
See the
<a href="http://www.monotone.ca/">Monotone website</a> for information
on monotone.
See
<a href="http://forum.i2p/viewtopic.php?t=2524">this forum post on i2p monotone</a>
<a href="http://{{ forum }}/viewtopic.php?t=2524">this forum post on i2p monotone</a>
for more information on how to get started and check out the source anonymously.
There is also a quick-start guide on the
<a href="{{ site_url('volunteer/guides/newdevelopers') }}">new developer's page</a>.
<a href="{{ newdevs }}">new developer's page</a>.
{%- endtrans %}</p>
<p>{% trans -%}
@@ -17,7 +18,7 @@ If you want to get the source non-anonymously, pull from the public server mtn.w
The i2p source code branch is "i2p.i2p".
{%- endtrans %}</p>
<h2>{% trans %} Guide {% endtrans %}</h2>
<h2>{% trans %}Guide{% endtrans %}</h2>
<p>{%- trans %}
The following is a detailed guide by Complication.
{%- endtrans %}</p>

65
i2p2www/pages/site/misc/upgrade-0.6.1.30.html
View File

@@ -1,64 +1,73 @@
{% extends "global/layout.html" %}
{% block title %}How to Upgrade from 0.6.1.30 and Earlier{% endblock %}
{% block title %}{% trans %}How to Upgrade from 0.6.1.30 and Earlier{% endtrans %}{% endblock %}
{% block content %}
<p>
&#149;
2008-02-05: <b>{% trans %}Upgrading from 0.6.1.30 and Earlier Releases{% endtrans %}</b>
</p>
<p>{% trans -%}
<p>{% trans jrandom=site_url('misc/jrandom-awol') -%}
Since i2p's lead developer
<a href="{{ site_url('misc/jrandom-awol') }}">has gone AWOL</a>,
<a href="{{ jrandom }}">has gone AWOL</a>,
we do not have his update signing key or access to
www.i2p[.net] or dev.i2p[.net].
Complication and zzz have generated new signing keys, and they and Amiga are providing
update file hosting. These changes must be configured in your router to take effect.
{%- endtrans %}</p>
<p>{% trans -%}
Make the following configuration changes and your router will automatically install
the latest release.
{%- endtrans %}</p>
<p>{% trans -%}
<p>{% trans downloads=get_url('downloads_list') -%}
We recommend the automated process as it will verify the key of the signed update file.
If you do not make these changes,
you may manually download the i2pupdate.zip file from{% endtrans %}
<a href="{{ url_for('downloads_list', lang=g.lang) }}">the download page</a>.
<ol><li>
you may manually download the i2pupdate.zip file from
<a href="{{ downloads }}">the download page</a>.
{%- endtrans %}</p>
<ol>
<li>
On
<a href="http://localhost:7657/configupdate.jsp">configupdate.jsp</a>:
</li><ol type="a"><li>
Change the News URL to: http://complication.i2p/news.xml
</li><li>
<ol type="a">
<li>{% trans url='http://complication.i2p/news.xml' -%}
Change the News URL to: {{ url }}
{%- endtrans %}</li>
<li>
{% trans %}Select ONE of the following new Update URLs at random and enter it into the Update URL box: {% endtrans %}
<br />http://amiga.i2p/i2p/i2pupdate.sud
<br />http://complication.i2p/i2p/i2pupdate.sud
<br />http://stats.i2p/i2p/i2pupdate.sud
</li><li>
Check the box "Update through the eepProxy?"
</li><li>
Click "Save"
</li></ol>
</li>
<li>{% trans %}Check the box "Update through the eepProxy?"{% endtrans %}</li>
<li>{% trans %}Click "Save"{% endtrans %}</li>
</ol>
</li>
<li>
On
<a href="http://localhost:7657/configadvanced.jsp">configadvanced.jsp</a>:
<ol type="a"><li>
Add the following line:
<ol type="a">
<li>{% trans %}Add the following line:{% endtrans %}
<br />
<textarea rows="1" cols="80" readonly="readonly" wrap="off">router.trustedUpdateKeys=W4kJbnv9KSVwbnapV7SaNW2kMIZKs~hwL0ro9pZXFo1xTwqz45nykCp1HM7sAKYDZay5z1HvYYOl9CNVz00xF03KPU9RUCVxhDZ1YXhZIskPKjUPUsCIpE~Z1C~N9KSEV6~2stDlBNH10VZ4T0X1TrcXwb3IBXliWo2y2GAx~Ow=,lT54eq3SH0TWWwQ1wgH6XPelIno7wH7UfiZOpQg-ZuxdNhc4UjjrohKdKZqfswt1ANPnmOlMewLGBESl7kJB9c5sByz~IOlNyz5BMLRC~R~ZC9QI4WXwUBYW8BhYO2mkvtdOrcy690lDkwzdf5xLxlCBpQlTaLYzQVjVWBcvbCA=,JHFA0yXUgKtmhajXFZH9Nk62OPRHbvvQHTi8EANV-D~3tjLjaz9p9cs6Fs8W3FSLfUwsQeFg7dfVSQQZga~1jMjboo94vIcm3j6XbW4mbcorVQ74uPjd8EA1AQhJ6bBTxDAFk~6fVDOdhHT0Wo5CcUn7v8bAYY3x3UWiL8Remx0=</textarea>
</li><li>
Click "Apply"
</li></ol>
<li>{% trans -%}You are now ready to automatically receive the release update file,
</li>
<li>{% trans %}Click "Apply"{% endtrans %}</li>
</ol>
</li>
<li>{% trans -%}
You are now ready to automatically receive the release update file,
either by setting your update policy to "download and install" or by clicking on the
"update available" link when it appears.
{%- endtrans %}</li></li></ol>
</p>
<p>{% trans -%}
{%- endtrans %}</li>
</ol>
<p>{% trans url='http://'+i2pconv('stats.i2p')+'/i2p/signingkeys.html' -%}
If you would like to verify the trusted update keys, they are also
<a href="http://stats.i2p/i2p/signingkeys.html">posted and signed here</a>.
<a href="{{ url }}">posted and signed here</a>.
Thank you for your support during this transition. For help please contact us on #i2p.
{%- endtrans %}</p>
<p>{% trans -%}
Amiga, Complication, welterde, zzz
{%- endtrans %}</p>
<p>Amiga, Complication, welterde, zzz</p>
{% endblock %}