139 lines
6.8 KiB
HTML
139 lines
6.8 KiB
HTML
<p>{% trans -%}
|
|
Your web browser will need to be configured in order to browse web sites on I2P
|
|
and to utilize the outproxies available within I2P. Below are walkthroughs for
|
|
some of the most popular browsers.
|
|
{%- endtrans %}</p>
|
|
|
|
<h2>{{ _('Firefox Profile for Windows') }}</h2>
|
|
<p>{% trans profile='/firefox' -%}
|
|
If you are using Windows, the recommended way of accessing I2P is using the
|
|
<a href='{{ profile }}'>Firefox profile</a>.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
If you do not wish to use that profile or are not on Windows, you need to
|
|
configure your browser yourself. Read below on how to that.
|
|
{%- endtrans %}</p>
|
|
|
|
<h2>{{ _('How to configure your browser') }}</h2>
|
|
|
|
<ul>
|
|
<li><a href="#firefox">Firefox</a></li>
|
|
<li><a href="#chrome">Chrome</a></li>
|
|
<li><a href="#ie8">Internet Explorer 8</a></li>
|
|
<li><a href="#TOS">{{ _('Outproxy Terms Of Service') }}</a></li>
|
|
</ul>
|
|
|
|
<a name="firefox"></a>
|
|
<h3>Firefox</h3>
|
|
<h4>{% trans %}Experimental, extension-based Configuration{% endtrans %}</h4>
|
|
<p>{% trans %}A new way of automatically configuring the I2P Browser is
|
|
currently being tested. It uses the Firefox's "Container Tabs" to build private
|
|
browsing tools for use with I2P and I2P applications.{% endtrans %}</p>
|
|
<p>{% trans %}It does pre-configuration of your browser by enabling some of
|
|
the privacy Browser Settings like ResistFingerprinting, and enforces WebRTC proxy
|
|
obedience. It also contains menus, shortcuts, and monitoring tools improving
|
|
Firefox's integration with I2P. It is a by-product of the I2P Browser project.
|
|
{% endtrans %}</p>
|
|
<p>{% trans %}The extension, <a href="https://addons.mozilla.org/en-US/firefox/addon/i2p-in-private-browsing/">I2P in Private Browsing</a>,
|
|
can be obtained from the Mozilla addon store.
|
|
{% endtrans %}</p>
|
|
<h4>{% trans %}Instructions for Firefox 57 and above:{% endtrans %}</h4>
|
|
<p>{% trans -%}
|
|
From the Menu button in the top right, select <em>Preferences</em>.
|
|
Scroll down until you see the <em>Network Proxy</em> section, as shown in the
|
|
screenshot below. Click on <em>Settings</em>
|
|
{%- endtrans %}</p>
|
|
<img src="{{ url_for('static', filename='images/firefox57.preferences.png') }}"
|
|
alt="{{ _('Firefox57 Network Options') }}" title="{{ _('Firefox57 Network Options') }}">
|
|
<p>{% trans -%}
|
|
In the <em>Connection Settings</em> pop-up, select <em>Manual proxy
|
|
configuration</em>. Set both the HTTP and SSL Proxy to address
|
|
<code>127.0.0.1</code> with port <code>4444</code> as shown in the following
|
|
screenshot.
|
|
{%- endtrans %}</p>
|
|
<img src="{{ url_for('static',
|
|
filename='images/firefox57.connectionsettings.png') }}" alt="{{ _('Firefox57
|
|
Connection Settings') }}" title="{{ _('Firefox57 Connection Settings') }}">
|
|
<p>{% trans -%}
|
|
Finally, go to the address <em>about:config</em> and find the property
|
|
media.peerConnection.ice.proxy_only. Ensure that this setting is True.
|
|
{%- endtrans %}</p>
|
|
<img src="{{ url_for('static',
|
|
filename='images/firefox.webrtc.png') }}" alt="{{ _('Firefox57
|
|
PeerConnection Settings') }}" title="{{ _('Firefox57 PeerConnection Settings') }}">
|
|
|
|
<a name="chrome"></a>
|
|
<h3>{% trans %} Chrome {% endtrans %}</h3>
|
|
<h4>{% trans %}Experimental, extension-based Configuration{% endtrans %}</h4>
|
|
<p>{% trans %}An experimental, partially-automated configuration process for
|
|
Chrome is available. In order to configure it, create a new <em>Profile</em>
|
|
especially for your I2P browsing, separate from the default profile. Then install
|
|
this <a href=""><em>Extension</em></a> in your newly-created profile. This profile
|
|
is now configured to use I2P. Highly detailed instructions are available at the
|
|
<a href="https://eyedeekay.github.io/I2P-Configuration-for-Chromium">homepage.</a>
|
|
{% endtrans %}</p>
|
|
<h4>{% trans %}All Chrome Versions{% endtrans %}</h4>
|
|
<p>{% trans -%}
|
|
Chromium-Based Browsers like Chrome have slightly different places for their
|
|
proxy settings depending on variant and platform. These instructions may be
|
|
slightly different in Brave or Iridium, for instance. From the <em>Main</em>
|
|
menu, navigate to the <em>Settings</em>, and search for the <em></em> menu item.
|
|
Clicking it will open the right settings for your platform.
|
|
{%- endtrans %}</p>
|
|
<img src="{{ url_for('static', filename='images/chrome.proxy.png') }}" alt="{{ _('Chrome Proxy Options') }}" title="{{ _('Chrome Proxy Options') }}">
|
|
<p>{% trans -%}
|
|
On Windows, this button will launch you into the shared proxy settings used
|
|
by <a href="#ie8"><em>Internet Explorer</em></a>, and you can configure it by
|
|
following the Internet Explorer 8 guide.
|
|
{%- endtrans %}</p>
|
|
<!---->
|
|
|
|
<a name="ie8"></a>
|
|
<h3>{{ _('Internet Explorer') }}</h3>
|
|
<p>{% trans -%}
|
|
In the start menu search for the the "Network and Internet Settings" to open the
|
|
settings. The last entry in the menu is the Proxy Settings, click it to
|
|
your proxy to connect to I2P.
|
|
{%- endtrans %}</p>
|
|
<img src="{{ url_for('static', filename='images/ie.options.png') }}" alt="{{ _('IE Internet Options') }}" title="{{ _('IE Internet Options') }}">
|
|
<p>{% trans -%}
|
|
Now set the checkmark at "use a proxy server for your LAN" and at the "Bypass
|
|
proxy server for local addresses". With a click on Advanced-button you open the
|
|
window to open the ports. Enter the values like on the picture, IP 127.0.0.1
|
|
and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save the
|
|
settings and your browser is set to use the I2P proxy.
|
|
{%- endtrans %}</p>
|
|
<img src="{{ url_for('static', filename='images/ie.proxyports.png') }}" alt="{{ _('IE Proxy Settings') }}" title="{{ _('IE Proxy Settings') }}">
|
|
|
|
|
|
<a name="TOS"></a>
|
|
<h3>{{ _('Outproxy Terms Of Service') }}</h3>
|
|
<p>{% trans -%}
|
|
Remember: I2P was not designed for creating proxies to the outer Internet.
|
|
Instead, it is meant to be used as an internal network.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
<p><b>The I2P project itself does not run any proxies to the Internet.</b>
|
|
The only outproxy is a service from the privacy solutions project.
|
|
Consider donating to them for a continued stable service. Increased funding will
|
|
allow them to improve this service. </p>
|
|
<a href="http://privacysolutions.no"
|
|
target="_blank">http://privacysolutions.no</a>
|
|
{%- endtrans %}</p>
|
|
<p>{% trans http='false.i2p', https='outproxy-tor.meeh.i2p' -%}
|
|
By default, I2P comes with two outproxies configured: <code>{{ http }}</code>
|
|
and <code>{{ https }}</code>. Even the domain names are different, it's the same outproxy you hit.
|
|
(multi-homed/keyed for better performance)
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
Filtering is active on these outproxies (for example, mibbit and torrent
|
|
tracker access is blocked). Eepsites
|
|
that are accessible via .i2p addresses are also not allowed via the outproxies.
|
|
As a convenience, the outproxy blocks ad servers.
|
|
{%- endtrans %}</p>
|
|
<p>{% trans -%}
|
|
<a href="https://www.torproject.org">Tor</a> is a good application to use as an
|
|
outproxy to the Internet.
|
|
{%- endtrans %}</p>
|
|
<!-- vim: set noai ff=unix nosi ft=html tw=79 et sw=4 ts=4 spell spelllang=en: -->
|