diff --git a/i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst b/i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst index 1350462d..44ff163c 100644 --- a/i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst +++ b/i2p2www/blog/2019/06/02/basic-tunnel-tutorial.rst @@ -4,11 +4,11 @@ :excerpt: {% trans %}Basic i2ptunnel Setup{% endtrans %} =================================================================== -{% trans -%}Basic i2p Tunnels Tutorial with Pictures{%- endtrans %} +{% trans -%}Basic I2P Tunnels Tutorial with Pictures{%- endtrans %} =================================================================== {% trans -%} -Although the Java i2p router comes pre-configured with a static web server, +Although the Java I2P router comes pre-configured with a static web server, jetty, to provide the user's first eepSite, many require more sophisticated functionality from their web server and would rather create an eepSite with a different server. This is of course possible, and actually is really easy once @@ -24,16 +24,16 @@ posed by improperly configured applications see: `Riseup here: `__, `Whonix Here: `__, `This blog article for some opsec fails: `__, -`and the i2p applications page here `__. +`and the I2P applications page here `__. Although much of this information is expressed for Tor Onion Services, the same -procedures and principles apply to hosting applications over i2p. +procedures and principles apply to hosting applications over I2P. {%- endtrans %} {% trans -%}Step One: Open the Tunnel Wizard{%- endtrans %} ----------------------------------------------------------- {% trans -%} -Go to the i2p web interface at 127.0.0.1:7657 and open the +Go to the I2P web interface at 127.0.0.1:7657 and open the `Hidden Services Manager `__\ (links to localhost). Click the button that says "Tunnel Wizard" to begin. {%- endtrans %} @@ -113,7 +113,7 @@ available. ---------------------------------------------------------------------- {% trans -%} -i2p provides a detailed panel for configuring the http server tunnel in custom +I2P provides a detailed panel for configuring the http server tunnel in custom ways. I'll finish this tutorial by walking through all of them. Eventually. {%- endtrans %} diff --git a/i2p2www/blog/2019/06/02/mirroring-guide.rst b/i2p2www/blog/2019/06/02/mirroring-guide.rst index e615f751..1b406040 100644 --- a/i2p2www/blog/2019/06/02/mirroring-guide.rst +++ b/i2p2www/blog/2019/06/02/mirroring-guide.rst @@ -354,7 +354,7 @@ special services for discovering new human-readable addresses, such as no.i2p, inr.i2p, and stats.i2p. These are sometimes known as Address helpers or Jump Services, and can also be subscribed to automatically. This may be espescially helpful to users of your service who wish to acquire the address without leaving -i2p or visiting your clearnet service. +I2P or visiting your clearnet service. {%- endtrans %} - `{% trans -%}Register a name with stats.i2p{%- endtrans %} `__ diff --git a/i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst b/i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst index ba351c7c..694338b1 100644 --- a/i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst +++ b/i2p2www/blog/2019/06/15/i2p-i2pd-ssh-config.rst @@ -4,12 +4,12 @@ :excerpt: SSH over I2P ===================================================================================== -{% trans -%}How to set up an ssh server behind i2p for personal access{%- endtrans %} +{% trans -%}How to set up an ssh server behind I2P for personal access{%- endtrans %} ===================================================================================== {% trans -%} -This is a tutorial on how to set up and tweak an i2p tunnel in order to use it -to access an SSH server remotely, using either i2p or i2pd. For now, it assumes +This is a tutorial on how to set up and tweak an I2P tunnel in order to use it +to access an SSH server remotely, using either I2P or i2pd. For now, it assumes you will install your SSH server from a package manager and that it's running as a service. {%- endtrans %} @@ -18,7 +18,7 @@ as a service. Considerations: In this guide, I'm assuming a few things. They will need to be adjusted depending on the complications that arise in your particular setup, especially if you use VM's or containers for isolation. This assumes that the -i2p router and the ssh server are running on the same localhost. You should be +I2P router and the ssh server are running on the same localhost. You should be using newly-generated SSH host keys, either by using a freshly installed sshd, or by deleting old keys and forcing their re-generation. For example: {%- endtrans %} @@ -32,14 +32,14 @@ or by deleting old keys and forcing their re-generation. For example: sudo ssh-keygen -N "" -t ecdsa -f /etc/ssh/ssh_host_ecdsa_key sudo ssh-keygen -N "" -t ed25519 -f /etc/ssh/ssh_host_ed25519_key -{% trans -%}Step One: Set up i2p tunnel for SSH Server{%- endtrans %} +{% trans -%}Step One: Set up I2P tunnel for SSH Server{%- endtrans %} --------------------------------------------------------------------- -{% trans -%}Using Java i2p{%- endtrans %} +{% trans -%}Using Java I2P{%- endtrans %} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ {% trans -%} -Using java i2p's web interface, navigate to the (Links to your Router Console)\ `Hidden Services Manager `__ +Using java I2P's web interface, navigate to the (Links to your Router Console)\ `Hidden Services Manager `__ and start the tunnel wizard. {%- endtrans %} @@ -135,7 +135,7 @@ tunnels.conf i2cp.reduceOnIdle = true keys = ssh-in.dat -{% trans -%}Restart your i2p router{%- endtrans %} +{% trans -%}Restart your I2P router{%- endtrans %} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ {% trans -%}Step Two: Set up SSH server{%- endtrans %} @@ -156,23 +156,23 @@ you should change AddressFamily to inet and ListenAddress to 127.0.0.1. {% trans -%} If you choose to use a port other than 22 for your SSH server, you will need to -change the port in your i2p tunnel configuration. +change the port in your I2P tunnel configuration. {%- endtrans %} -{% trans -%}Step Three: Set up i2p tunnel for SSH Client{%- endtrans %} +{% trans -%}Step Three: Set up I2P tunnel for SSH Client{%- endtrans %} ----------------------------------------------------------------------- {% trans -%} -You will need to be able to see the i2p router console of the SSH server in +You will need to be able to see the I2P router console of the SSH server in order to configure your client connection. One neat thing about this setup is -that the initial connection to the i2p tunnel is authenticated, somewhat +that the initial connection to the I2P tunnel is authenticated, somewhat reducing the risk of your initial connection to the SSH server being MITM'ed, as is a risk in Trust-On-First-Use scenarios. {%- endtrans %} -.. _using-java-i2p-1: +.. _using-java-I2P-1: -{% trans -%}Using Java i2p{%- endtrans %} +{% trans -%}Using Java I2P{%- endtrans %} ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. _tunnel-wizard-1: @@ -202,7 +202,7 @@ Give it a good description. {% trans -%} This is the only slightly tricky part. Go to the hidden services manager of the -i2p router console and find the base64 "local destination" of the SSH server +I2P router console and find the base64 "local destination" of the SSH server tunnel. You'll need to find a way to copy this information into the next step. I generally `Tox `__ it to myself, any off-the-record should be sufficient for most people. @@ -267,17 +267,17 @@ adjust it for your performance/anonymity needs. inbound.backupQuantity = 2 outbound.backupQuantity = 2 i2cp.dontPublishLeaseSet = true - destination = bubfjkl2l46pevgnh7yicm2e7rkld4jrgpmruw2ueqn5fa4ag6eq.b32.i2p + destination = bubfjkl2l46pevgnh7yicm2e7rkld4jrgpmruw2ueqn5fa4ag6eq.b32.I2P keys = ssh-in.dat -{% trans -%}Restart the i2p router on the client{%- endtrans %} +{% trans -%}Restart the I2P router on the client{%- endtrans %} ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ {% trans -%}Step Four: Set up SSH client{%- endtrans %} ------------------------------------------------------- {% trans -%} -There are lots of ways to set up an SSH client to connect to your server on i2p, +There are lots of ways to set up an SSH client to connect to your server on I2P, but there are a few things you should do to secure your SSH client for anonymous use. First, you should configure it to only identify itself to SSH server with a single, specific key so that you don't risk contaminating your anonymous and @@ -297,7 +297,7 @@ Make sure your $HOME/.ssh/config contains the following lines: {% trans -%} Alternatively, you could make a .bash_alias entry to enforce your options and -automatically connect to i2p. You get the idea, you need to enforce +automatically connect to I2P. You get the idea, you need to enforce IdentitiesOnly and provide an identity file. {%- endtrans %} diff --git a/i2p2www/pages/site/index.html b/i2p2www/pages/site/index.html index 8d3c2cf7..02dbb83e 100644 --- a/i2p2www/pages/site/index.html +++ b/i2p2www/pages/site/index.html @@ -15,7 +15,11 @@
  • {% trans -%}I2P is an anonymizing network, offering a simple layer that identity-sensitive applications can use to securely communicate. {% endtrans %}
    • -
  • {% trans -%}I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as people with nothing to hide. +
  • {% trans -%}I2P is used by many people who care about their privacy: +activists, oppressed people, journalists and whistleblowers. +{% endtrans %}
    • +
  • {% trans -%}It is for everyone and an alternative to the internet +because it solves issues like privacy and censorship. {% endtrans %}
  • {% trans -%}All data is wrapped with several layers of encryption, and the network is both distributed and dynamic, with no trusted parties. {% endtrans %}
    • diff --git a/i2p2www/static/styles/duck/default.css b/i2p2www/static/styles/duck/default.css index 6c3c3638..7580852c 100644 --- a/i2p2www/static/styles/duck/default.css +++ b/i2p2www/static/styles/duck/default.css @@ -149,7 +149,6 @@ div#content .main p { div#content .aside-wrap { width: 80%; margin: 1.25em auto; - display: inline-block; } div#content .aside {