kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Updated information about FTP proxy, and outproxy situation.

Browse Source
This commit is contained in:
meeh
2014-08-11 21:02:15 +00:00
parent a4810e15a2
commit a43a956be0
1 changed files with 13 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -32,6 +32,7 @@ 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.
<b>Note/Privacy tip:</b> Set the FTP proxy to the same settings as the HTTP proxy.
{%- endtrans %}</p>
<img src="{{ url_for('static', filename='images/ie.proxyports.jpg') }}" alt="{{ _('IE Proxy Settings') }}" title="{{ _('IE Proxy Settings') }}">
@@ -49,6 +50,7 @@ In the <em>Connection Settings</em> window, click the circle next to <em>Manual
proxy configuration</em>, then enter 127.0.0.1, port 4444 in the HTTP Proxy
field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.
Be sure to enter localhost and 127.0.0.1 into the "No Proxy for" box.
<b>Note/Privacy tip:</b> Set the FTP proxy to the same settings as the HTTP proxy.
{%- endtrans %}</p>
<img src="{{ url_for('static', filename='images/firefox.proxyports.jpg') }}" alt="{{ _('Firefox Proxy Settings') }}" title="{{ _('Firefox Proxy Settings') }}">
@@ -64,6 +66,7 @@ configuration" on the right.
Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port 4445 into
HTTPS box. Enter <code>127.0.0.1,localhost</code> into the Exceptions box. Click Apply then OK
to close the configuration window.
<b>Note/Privacy tip:</b> Set the FTP proxy to the same settings as the HTTP proxy.
{%- endtrans %}</p>
<a name="TOS"></a>
@@ -73,26 +76,23 @@ 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 -%}
<b>The I2P project itself does not run any proxies to the Internet. Any such proxy
services are run by by private volunteers and could be shut down or
unreachable at anytime.</b>
<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. Higher bandwidth will
increase with the founding of the organization. Maybe more outproxies too.</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>
(an HTTP-only proxy) and <code>{{ https }}</code> (an HTTPS proxy
routed through Tor.
{%- endtrans %}</p>
<p>{% trans -%}
Both of these outproxies are configured with connection limits. This means
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!
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, <code>false.i2p</code> blocks ad servers.
As a convenience, the outproxy blocks ad servers.
{%- endtrans %}</p>
<p>{% trans -%}
<a href="https://www.torproject.org">Tor</a> is good application to use as an