|
|
|
|
@ -2,19 +2,31 @@
|
|
|
|
|
{%- from "downloads/macros" import package_outer with context -%}
|
|
|
|
|
{% block title %}Firefox Profile{% endblock %}
|
|
|
|
|
{% block content %}
|
|
|
|
|
|
|
|
|
|
<h1>{{ _('I2P Firefox Browser Profile') }}</h1>
|
|
|
|
|
<p>{% trans -%}
|
|
|
|
|
Now that you have joined the I2P network, you will want to see I2P Sites and and
|
|
|
|
|
other content that is hosted on the network. The Firefox browser profile is
|
|
|
|
|
pre-configured to allow you to access the content available on the network. It
|
|
|
|
|
also keeps your I2P search activity separate from your internet search activity.
|
|
|
|
|
pre-configured to allow you to access the content available on the network.
|
|
|
|
|
{%- endtrans %}</p>
|
|
|
|
|
<h2>{{ _('Why should I use it?') }}</h2>
|
|
|
|
|
<p>{% trans -%}
|
|
|
|
|
WHAT IS WRONG?
|
|
|
|
|
Browsers are highly complex and powerful engines for executing code and displaying
|
|
|
|
|
information obtained mainly from strangers on the internet. By default, they
|
|
|
|
|
tend to leak a great deal of information about the person using them to the servers
|
|
|
|
|
they retrieve information from. Using this browser profile allows you to become
|
|
|
|
|
part of a "common" set of very similar browser users, instead of appearing unique
|
|
|
|
|
or revealing details of your hardware or software. Because this involves disabling
|
|
|
|
|
some browser features, this also reduces the attack surface available to outsiders.
|
|
|
|
|
This keeps you safer while browsing the Invisible Web.
|
|
|
|
|
{%- endtrans %}</p>
|
|
|
|
|
<p>{% trans -%}
|
|
|
|
|
This browser profile also includes both the NoScrpt and HTTPSEverywhere plugin for
|
|
|
|
|
better protection Javascript based attacks and HTTPS support where available.
|
|
|
|
|
<h2>{{ _('How do I use it?') }}</h2>
|
|
|
|
|
<p>{% trans guideurl=get_url('downloads_windows'), postfilename=pver('I2P-Profile-Installer-%s.exe') -%}
|
|
|
|
|
First, download and install <a href="{{ guideurl }}">I2P for Windows</a>. Then,
|
|
|
|
|
download the Firefox browser profile using the green button just below, and run
|
|
|
|
|
the <code>{{ postfilename }}</code> by double-clicking it. Finally, start Firefox
|
|
|
|
|
with the preconfigured Firefox profile using the shortcut on the desktop or in
|
|
|
|
|
the start menu.
|
|
|
|
|
{%- endtrans %}</p>
|
|
|
|
|
|
|
|
|
|
{%- set name = 'Windows' -%}
|
|
|
|
|
@ -46,4 +58,45 @@ The files are signed by {{ signer }},
|
|
|
|
|
<a href="{{ signingkey }}">whose key is here</a>.
|
|
|
|
|
{%- endtrans %}
|
|
|
|
|
|
|
|
|
|
<h2>{{ _('What is in it?') }}</h2>
|
|
|
|
|
<p>{% trans -%}
|
|
|
|
|
This browser profile also includes both the NoScript and HTTPSEverywhere plugin for
|
|
|
|
|
better protection Javascript based attacks and HTTPS support where available. It
|
|
|
|
|
also keeps your I2P search activity separate from your visible internet search
|
|
|
|
|
activity. The profile configures the I2P Proxy for all sites and browser features.
|
|
|
|
|
I2P In Private Browsing is used to provide I2P-Specific browser integrations.
|
|
|
|
|
{%- endtrans %}</p>
|
|
|
|
|
<h3>{{ _('Source Code and Issue Tracking') }}</h3>
|
|
|
|
|
<div>{% trans -%}
|
|
|
|
|
If you would like to examine the source code for individual components, you may
|
|
|
|
|
find it on i2pgit.org or github.com. The license for each respective component
|
|
|
|
|
can be found in the license directory of the <code>i2p.firefox</code> project.
|
|
|
|
|
{%- endtrans %}</div>
|
|
|
|
|
<div><a href="https://i2pgit.org/i2p-hackers/i2p.firefox">{% trans -%}Gitlab Repository{%- endtrans %}</a></div>
|
|
|
|
|
<div><a href="https://github.com/i2p/i2p.firefox">{% trans -%}Github Repository{%- endtrans %}</a></div>
|
|
|
|
|
<div>{% trans -%}
|
|
|
|
|
If you wish to file an issue about the Firefox profile, please use Gitlab to
|
|
|
|
|
contact us. For security-sensitive issues, please remember to check the
|
|
|
|
|
"This issue is confidential and should only be visible to team members with at least Reporter access"
|
|
|
|
|
option when filing the issue.
|
|
|
|
|
{%- endtrans %}</div>
|
|
|
|
|
<div><a href="https://i2pgit.org/i2p-hackers/i2p.firefox/issues">{% trans -%}Gitlab Repository{%- endtrans %}</a></div>
|
|
|
|
|
<h2>{{ _('How is it different from Tor Browser?') }}</h2>
|
|
|
|
|
<p>{% trans -%}
|
|
|
|
|
This is not a fork of Firefox. Instead, it is a browser profile with pre-configured
|
|
|
|
|
settings. That means that it requires Firefox(Or Tor Browser) to be installed
|
|
|
|
|
before you can use it. This is for security reasons, it is important that you are
|
|
|
|
|
able to recieve reliable updates from a trustworthy vendor. As much as we would
|
|
|
|
|
like to, we can't maintain a whole Firefox fork and provide timely updates for
|
|
|
|
|
it right now.
|
|
|
|
|
{%- endtrans %}</p>
|
|
|
|
|
<p>{% trans -%}
|
|
|
|
|
I2P routers are designed to have long uptimes, and so unlike Tor Browser, the
|
|
|
|
|
lifetime of your I2P Router is not tied to the lifetime of your I2P browsing
|
|
|
|
|
session. The browser profile will manage your history, your browser's local
|
|
|
|
|
storage and cache, and your browsing context but it will never stop your I2P
|
|
|
|
|
router on it's own. You may stop the router using the web interface on the
|
|
|
|
|
router console homepage.
|
|
|
|
|
{%- endtrans %}</p>
|
|
|
|
|
|
|
|
|
|
{% endblock %}
|
|
|
|
|
|
idk