forked from I2P_Developers/i2p.www
Make cases consistent across blog posts
This commit is contained in:
@@ -4,11 +4,11 @@
|
|||||||
:excerpt: {% trans %}Basic i2ptunnel Setup{% endtrans %}
|
:excerpt: {% trans %}Basic i2ptunnel Setup{% endtrans %}
|
||||||
|
|
||||||
===================================================================
|
===================================================================
|
||||||
{% trans -%}Basic i2p Tunnels Tutorial with Pictures{%- endtrans %}
|
{% trans -%}Basic I2P Tunnels Tutorial with Pictures{%- endtrans %}
|
||||||
===================================================================
|
===================================================================
|
||||||
|
|
||||||
{% trans -%}
|
{% 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
|
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
|
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
|
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: <https://riseup.net/en/security/network-security/tor/onionservices-best-practices>`__,
|
`Riseup here: <https://riseup.net/en/security/network-security/tor/onionservices-best-practices>`__,
|
||||||
`Whonix Here: <https://www.whonix.org/wiki/Onion_Services>`__,
|
`Whonix Here: <https://www.whonix.org/wiki/Onion_Services>`__,
|
||||||
`This blog article for some opsec fails: <https://blog.0day.rocks/securing-a-web-hidden-service-89d935ba1c1d>`__,
|
`This blog article for some opsec fails: <https://blog.0day.rocks/securing-a-web-hidden-service-89d935ba1c1d>`__,
|
||||||
`and the i2p applications page here <https://geti2p.net/en/docs/applications/supported>`__.
|
`and the I2P applications page here <https://geti2p.net/en/docs/applications/supported>`__.
|
||||||
Although much of this information is expressed for Tor Onion Services, the same
|
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 %}
|
{%- endtrans %}
|
||||||
|
|
||||||
{% trans -%}Step One: Open the Tunnel Wizard{%- endtrans %}
|
{% trans -%}Step One: Open the Tunnel Wizard{%- endtrans %}
|
||||||
-----------------------------------------------------------
|
-----------------------------------------------------------
|
||||||
|
|
||||||
{% trans -%}
|
{% 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 <http://127.0.0.1:7657/i2ptunnelmgr>`__\ (links to
|
`Hidden Services Manager <http://127.0.0.1:7657/i2ptunnelmgr>`__\ (links to
|
||||||
localhost). Click the button that says "Tunnel Wizard" to begin.
|
localhost). Click the button that says "Tunnel Wizard" to begin.
|
||||||
{%- endtrans %}
|
{%- endtrans %}
|
||||||
@@ -113,7 +113,7 @@ available.
|
|||||||
----------------------------------------------------------------------
|
----------------------------------------------------------------------
|
||||||
|
|
||||||
{% trans -%}
|
{% 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.
|
ways. I'll finish this tutorial by walking through all of them. Eventually.
|
||||||
{%- endtrans %}
|
{%- endtrans %}
|
||||||
|
|
||||||
|
@@ -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
|
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
|
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
|
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 %}
|
{%- endtrans %}
|
||||||
|
|
||||||
- `{% trans -%}Register a name with stats.i2p{%- endtrans %} <http://stats.i2p/i2p/addkey.html>`__
|
- `{% trans -%}Register a name with stats.i2p{%- endtrans %} <http://stats.i2p/i2p/addkey.html>`__
|
||||||
|
@@ -4,12 +4,12 @@
|
|||||||
:excerpt: SSH over I2P
|
: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 -%}
|
{% trans -%}
|
||||||
This is a tutorial on how to set up and tweak an i2p tunnel in order to use it
|
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
|
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
|
you will install your SSH server from a package manager and that it's running
|
||||||
as a service.
|
as a service.
|
||||||
{%- endtrans %}
|
{%- endtrans %}
|
||||||
@@ -18,7 +18,7 @@ as a service.
|
|||||||
Considerations: In this guide, I'm assuming a few things. They will need to be
|
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,
|
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
|
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,
|
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:
|
or by deleting old keys and forcing their re-generation. For example:
|
||||||
{%- endtrans %}
|
{%- 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 ecdsa -f /etc/ssh/ssh_host_ecdsa_key
|
||||||
sudo ssh-keygen -N "" -t ed25519 -f /etc/ssh/ssh_host_ed25519_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 -%}
|
{% trans -%}
|
||||||
Using java i2p's web interface, navigate to the (Links to your Router Console)\ `Hidden Services Manager <http://127.0.0.1:7657/i2ptunnelmgr>`__
|
Using java I2P's web interface, navigate to the (Links to your Router Console)\ `Hidden Services Manager <http://127.0.0.1:7657/i2ptunnelmgr>`__
|
||||||
and start the tunnel wizard.
|
and start the tunnel wizard.
|
||||||
{%- endtrans %}
|
{%- endtrans %}
|
||||||
|
|
||||||
@@ -135,7 +135,7 @@ tunnels.conf
|
|||||||
i2cp.reduceOnIdle = true
|
i2cp.reduceOnIdle = true
|
||||||
keys = ssh-in.dat
|
keys = ssh-in.dat
|
||||||
|
|
||||||
{% trans -%}Restart your i2p router{%- endtrans %}
|
{% trans -%}Restart your I2P router{%- endtrans %}
|
||||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||||
|
|
||||||
{% trans -%}Step Two: Set up SSH server{%- 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 -%}
|
{% trans -%}
|
||||||
If you choose to use a port other than 22 for your SSH server, you will need to
|
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 %}
|
{%- endtrans %}
|
||||||
|
|
||||||
{% trans -%}Step Three: Set up i2p tunnel for SSH Client{%- endtrans %}
|
{% trans -%}Step Three: Set up I2P tunnel for SSH Client{%- endtrans %}
|
||||||
-----------------------------------------------------------------------
|
-----------------------------------------------------------------------
|
||||||
|
|
||||||
{% trans -%}
|
{% 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
|
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,
|
reducing the risk of your initial connection to the SSH server being MITM'ed,
|
||||||
as is a risk in Trust-On-First-Use scenarios.
|
as is a risk in Trust-On-First-Use scenarios.
|
||||||
{%- endtrans %}
|
{%- endtrans %}
|
||||||
|
|
||||||
.. _using-java-i2p-1:
|
.. _using-java-I2P-1:
|
||||||
|
|
||||||
{% trans -%}Using Java i2p{%- endtrans %}
|
{% trans -%}Using Java I2P{%- endtrans %}
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
.. _tunnel-wizard-1:
|
.. _tunnel-wizard-1:
|
||||||
@@ -202,7 +202,7 @@ Give it a good description.
|
|||||||
|
|
||||||
{% trans -%}
|
{% trans -%}
|
||||||
This is the only slightly tricky part. Go to the hidden services manager of the
|
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.
|
tunnel. You'll need to find a way to copy this information into the next step.
|
||||||
I generally `Tox <https://tox.chat>`__ it to myself, any off-the-record
|
I generally `Tox <https://tox.chat>`__ it to myself, any off-the-record
|
||||||
should be sufficient for most people.
|
should be sufficient for most people.
|
||||||
@@ -267,17 +267,17 @@ adjust it for your performance/anonymity needs.
|
|||||||
inbound.backupQuantity = 2
|
inbound.backupQuantity = 2
|
||||||
outbound.backupQuantity = 2
|
outbound.backupQuantity = 2
|
||||||
i2cp.dontPublishLeaseSet = true
|
i2cp.dontPublishLeaseSet = true
|
||||||
destination = bubfjkl2l46pevgnh7yicm2e7rkld4jrgpmruw2ueqn5fa4ag6eq.b32.i2p
|
destination = bubfjkl2l46pevgnh7yicm2e7rkld4jrgpmruw2ueqn5fa4ag6eq.b32.I2P
|
||||||
keys = ssh-in.dat
|
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 -%}Step Four: Set up SSH client{%- endtrans %}
|
||||||
-------------------------------------------------------
|
-------------------------------------------------------
|
||||||
|
|
||||||
{% trans -%}
|
{% 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
|
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
|
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
|
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 -%}
|
{% trans -%}
|
||||||
Alternatively, you could make a .bash_alias entry to enforce your options and
|
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.
|
IdentitiesOnly and provide an identity file.
|
||||||
{%- endtrans %}
|
{%- endtrans %}
|
||||||
|
|
||||||
|
@@ -15,7 +15,11 @@
|
|||||||
<ul>
|
<ul>
|
||||||
<li>{% trans -%}I2P is an anonymizing network, offering a simple layer that identity-sensitive applications can use to securely communicate.
|
<li>{% trans -%}I2P is an anonymizing network, offering a simple layer that identity-sensitive applications can use to securely communicate.
|
||||||
{% endtrans %}</li>
|
{% endtrans %}</li>
|
||||||
<li>{% 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.
|
<li>{% trans -%}I2P is used by many people who care about their privacy:
|
||||||
|
activists, oppressed people, journalists and whistleblowers.
|
||||||
|
{% endtrans %}</li>
|
||||||
|
<li>{% trans -%}It is for everyone and an alternative to the internet
|
||||||
|
because it solves issues like privacy and censorship.
|
||||||
{% endtrans %}</li>
|
{% endtrans %}</li>
|
||||||
<li>{% trans -%}All data is wrapped with several layers of encryption, and the network is both distributed and dynamic, with no trusted parties.
|
<li>{% trans -%}All data is wrapped with several layers of encryption, and the network is both distributed and dynamic, with no trusted parties.
|
||||||
{% endtrans %}</li>
|
{% endtrans %}</li>
|
||||||
|
@@ -149,7 +149,6 @@ div#content .main p {
|
|||||||
div#content .aside-wrap {
|
div#content .aside-wrap {
|
||||||
width: 80%;
|
width: 80%;
|
||||||
margin: 1.25em auto;
|
margin: 1.25em auto;
|
||||||
display: inline-block;
|
|
||||||
}
|
}
|
||||||
|
|
||||||
div#content .aside {
|
div#content .aside {
|
||||||
|
Reference in New Issue
Block a user