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

Merge branch 'master' of i2pgit.org:i2p-hackers/i2p.www into style-guide

Browse Source
This commit is contained in:
idk
2020-11-24 10:49:20 -05:00
parent a25236f5fc 4f8d1508b3
commit 31988ee1e4
53 changed files with 19980 additions and 2025 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
findpochanges.sh
View File

@@ -6,8 +6,9 @@ for i in i2p2www/translations/*/*/*.po
do
if [ -d ./.git ]; then
git diff $i | grep '+msgstr' | grep -v '+msgstr ""' > $TMP
fi
else
mtn diff $i | grep '+msgstr' | grep -v '+msgstr ""' > $TMP
fi
if [ -s $TMP ]
then
echo $i >> $TMP2

1
i2p2www/pages/global/nav.html
View File

@@ -16,6 +16,7 @@
<li><a href="{{ site_url('docs/applications/gitlab') }}"><div class="menuitem"><span>{{ _('GitLab') }}</span></div></a></li>
<li><a href="{{ site_url('docs/applications/git') }}"><div class="menuitem"><span>{{ _('Git') }}</span></div></a></li>
<li><a href="{{ site_url('docs/applications/git-bundle') }}"><div class="menuitem"><span>{{ _('git+Bittorrent') }}</span></div></a></li>
<li><a href="{{ site_url('docs/applications/irc') }}"><div class="menuitem"><span>{{ _('IRC') }}</span></div></a></li>
</ul>
</li>
</ul>

5
i2p2www/pages/site/about/media.html
View File

@@ -1,6 +1,6 @@
{% extends "global/layout.html" %}
{% block title %}{{ _('Presentations on I2P') }}{% endblock %}
{% block lastupdated %}April 2016{% endblock %}
{% block lastupdated %}2020-11{% endblock %}
{% block content %}
<p>{% trans papers=site_url('papers') -%}
Following are links to presentations, videos, and tutorials about I2P. Links to research papers on I2P are available <a href="{{ papers }}">here</a>.
@@ -47,10 +47,11 @@ Lars Schimmer,
March 14-15, 2009
{%- endtrans %}</li>
<li>{% trans mp3='http://c2047862.cdn.cloudfiles.rackspacecloud.com/tnhc21.mp3' -%}
<li>{% trans mp3='http://stats.i2p/media/tnhc21.mp3', vid='https://www.youtube.com/watch?v=ADiZ32CkEao' -%}
HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of Adrian Hong's talk
"Hackers for Human Rights".
<a href="{{ mp3 }}">MP3 audio</a>
<a href="{{ vid }}">Youtube Video</a> (I2P part at 44 minutes)
{%- endtrans %}</li>
<li>{% trans link='http://www.irongeek.com/i.php?page=videos/shmoocon-firetalks-2011' -%}

25
i2p2www/pages/site/docs/api/samv3.html
View File

@@ -1,14 +1,23 @@
{% extends "global/layout.html" %}
{% block title %}SAM V3{% endblock %}
{% block lastupdated %}2020-10{% endblock %}
{% block lastupdated %}2020-11{% endblock %}
{% block accuratefor %}0.9.48{% endblock %}
{% block content %}
<p>Specified below is a simple client protocol for interacting with I2P.
<p>SAM is a simple client protocol for interacting with I2P.
SAM is the recommended protocol for non-Java applications to connect to the I2P network,
and is supported by multiple router implementations.
Java applications should use the streaming or I2CP APIs directly.
</p>
<p>SAM version 3
was introduced in I2P release 0.7.3.
was introduced in I2P release 0.7.3 (May 2009) and is a stable and supported interface.
3.1 is also stable and supports the signature type option, which is strongly recommended.
More recent 3.x versions support advanced features.
</p><p>
Alternatives:
<a href="{{ site_url('docs/api/bob') }}">BOB(unsupported)</a>.
<a href="socks">SOCKS</a>,
<a href="streaming">Streaming</a>,
<a href="{{ site_url('docs/protocol/i2cp') }}">I2CP</a>,
<a href="{{ site_url('docs/api/bob') }}">BOB (deprecated)</a>.
Older versions:
<a href="{{ site_url('docs/api/sam') }}">SAM V1</a>,
<a href="{{ site_url('docs/api/samv2') }}">SAM V2</a>,
@@ -107,7 +116,7 @@ Older versions:
<td>yes</td>
<td>yes</td>
<td>yes</td>
<td><a href="https://github.com/i2p/libsam3">github.com/i2p/libsam3</a></td>
<td><a href="https://github.com/i2p/libsam3">github.com/i2p/libsam3</a><br>(Maintained by the I2P project)</td>
</tr>
<tr class="odd">
<td>mooni2p</td>
@@ -187,7 +196,7 @@ can forward back I2P datagrams to the client's datagram server.
<h3>Version 3.1 Changes</h3>
<p>
Version 3.1 was introduced in I2P release 0.9.14. SAM 3.1 is the recommended
Version 3.1 was introduced in I2P release 0.9.14 (July 2014). SAM 3.1 is the recommended
minimum SAM implementation because of its support for better signature types
than SAM 3.0.
<ul>
@@ -200,7 +209,7 @@ than SAM 3.0.
<h3>Version 3.2 Changes</h3>
<p>
Version 3.2 was introduced in I2P release 0.9.24.
Version 3.2 was introduced in I2P release 0.9.24 (January 2016).
</p>
<h4>I2CP Port and Protocol Support</h4>
@@ -248,7 +257,7 @@ Version 3.2 was introduced in I2P release 0.9.24.
<h3>Version 3.3 Changes</h3>
<p>
Version 3.3 was introduced in I2P release 0.9.25.
Version 3.3 was introduced in I2P release 0.9.25 (March 2016).
<ul>
<li>The same session may be used for streams, datagrams, and raw simultaneously.
Incoming packets and streams will be routed based on I2P protocol and to-port.

235
i2p2www/pages/site/docs/applications/irc.html Normal file
View File

@@ -0,0 +1,235 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Configuring IRC Software{% endtrans %}{% endblock %}
{% block lastupdated %}2020-11{% endblock %}
{% block accuratefor %}0.9.47{% endblock %}
{% block content %}
<h1>{% trans %}IRC Software{% endtrans %}</h1>
<ul>
<li><a href="#clients">Clients</a></li>
<li><a href="#servers">Servers</a></li>
</ul>
<a name="clients"></a>
<h2>{% trans %}Clients{% endtrans %}</h2>
<p>{% trans %} There are many IRC clients that can be used with I2P. In
fact, all IRC clients can be connected to the Irc2P Service by connecting
them to the IRC Tunnel.{% endtrans %}</p>
<ul>
<li><a href="#pidgin">Pidgin(Windows, Linux) Adium(OSX)</a></li>
<li><a href="#xchat">XChat(Windows, Linux) XChat Aqua(OSX)</a></li>
<li><a href="#thunderbird">Thunderbird(Windows, Linux, OSX)</a></li>
<li><a href="#revolution">Revolution IRC(Android)</a></li>
<li><a href="#dispatch">Dispatch(Windows, Linux, OSX)(WebClient)</a></li>
</ul>
<h3>Check the IRC tunnel</h3>
<p>{% trans %}To configure any IRC client to chat on Irc2P, first, make sure that
your IRC tunnel is available. Visit the <a href="http://127.0.0.1:7657/i2ptunnel/">Hidden Services Manager</a>
and look for Irc2P in your "Client Tunnels" section. If the "Status" indicator on
the right-hand side is yellow or green, your Irc2P tunnel is ready and you should
proceed to the next step.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/tuncheck-irc-all.png') }}"
alt="{{ _('IRC Tunnel Check') }}" title="{{ _('IRC Tunnel Check') }}">
<p>{% trans %}Any IRC client can be connected to this IRC tunnel, but detailed
instructions for several popular clients are provided below.{% endtrans %}</p>
<a name="pidgin"></a>
<h3>Pidgin</h3>
<p>{% trans %}Pidgin is a very popular Instant Messaging client with built-in IRC
support. It is also possible to use it with many other kinds of chat service, and
it supports using multiple accounts at once and has a variety of plugin-ins. There
is a similar application for OSX called "Adium." The instructions for Pidgin are
similar in Adium.
{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/pidgin-irc-0.png') }}"
alt="{{ _('Open the menu') }}" title="{{ _('Pidgin Step One') }}">
<p>{% trans %}After launching Pidgin, you should see a "Buddy List" window. From
that window, open the "Accounts" menu from the toolbar. Select "Manage Accounts" to
begin configuring your I2P account.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/pidgin-irc-1.png') }}"
alt="{{ _('Add the account') }}" title="{{ _('Pidgin Step Two') }}">
<p>{% trans %}Click the "Add" button. In the window that opens, select "IRC" under
"Protocol," and set the "Host" to 127.0.0.1. Then pick a username and password. IRC
does not require you to register a nickname to join, but you may if you wish, after
you connect to Irc2P.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/pidgin-irc-2.png') }}"
alt="{{ _('Configure username, hostname, password') }}" title="{{ _('Pidgin Step Three') }}">
<p>{% trans %}Navigate to the "Advanced" tab and set the "Port" field to 6668 and
make sure that SSL is <em>disabled</em>, since your tunnel has encryption provided
by I2P.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/pidgin-irc-3.png') }}"
alt="{{ _('Configure port') }}" title="{{ _('Pidgin Step Four') }}">
<a name="xchat"></a>
<h3>XChat</h3>
<p>{% trans %}Open the Server List menu of XChat and click the "Add" button.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/xchat-irc-0.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('XChat Step One') }}">
<p>{% trans %}Create a new network named "Irc2P" to configure for I2P IRC. Click
the "Edit" button on the right-hand side.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/xchat-irc-1.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('XChat Step Two') }}">
<p>{% trans %}Change the value in "Servers" from the default to `localhost/6669`,
and configure the default channels you want to join. I suggest #i2p and #i2p-dev
{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/xchat-irc-2.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('XChat Step Three') }}">
<p>{% trans %}Close the "Edit Server" window from to return to the Server List
page and click "Connect" to join I2PRC.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/xchat-irc-3.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('XChat Step Four') }}">
<a name="thunderbird"></a>
<h3>Thunderbird</h3>
<p>{% trans %}Click on the "Chat" button in the toolbar at the top of the
Thunderbird window.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/thunderbird-irc-0.png') }}"
alt="{{ _('Add a chat') }}" title="{{ _('Thunderbird Step One') }}">
<p>{% trans %}Click the get started button to begin setting up Irc2P.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/thunderbird-irc-1.png') }}"
alt="{{ _('Get Started') }}" title="{{ _('Thunderbird Step Two') }}">
<p>{% trans %}In the first step, select "IRC" for your network type.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/thunderbird-irc-2.png') }}"
alt="{{ _('Pick IRC') }}" title="{{ _('Thunderbird Step Three') }}">
<p>{% trans %}Choose a nickname and set your IRC Server to 127.0.0.1, but do not
set a port.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/thunderbird-irc-3.png') }}"
alt="{{ _('Set username and server') }}" title="{{ _('Thunderbird Step Four') }}">
<p>{% trans %}Set a password if you want.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/thunderbird-irc-4.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('Thunderbird Step Five') }}">
<p>{% trans %}Configure the IRC Server with an alias like "Irc2P" and set the
port to 6668.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/thunderbird-irc-5.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('Thunderbird Step Six') }}">
<p>{% trans %}If your summary looks like this, then you're ready to connect
with Irc2P.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/thunderbird-irc-6.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('Thunderbird Step Seven') }}">
<a name="revolution"></a>
<h3>Revolution IRC</h3>
<p>{% trans %}Revolution IRC is an easy to use IRC client for Android. It's able to
handle multiple accounts on multiple services, so you can use it for Irc2P and for
your non-I2P IRC networks as well.{% endtrans %}</p>
<p>{% trans %}Click the "Add Server" button(Shaped like this: `+`) in the corner
to get started configuring Revolution IRC for I2P.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/revolution-irc-0.png') }}"
alt="{{ _('Add a server') }}" title="{{ _('Revolution Step One') }}">
<p>{% trans %}Fill in the server name, change the address to "127.0.0.1" and the
port to 6668.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/revolution-irc-1.png') }}"
alt="{{ _('Configure it like this') }}" title="{{ _('Revolution Step Two') }}">
<p>{% trans %}Give yourself a nickname and configure some channels to automatically
join.{% endtrans %}</p>
<img src="{{ url_for('static', filename='images/irc/revolution-irc-2.png') }}"
alt="{{ _('Open the menu') }}" title="{{ _('Revolution Step Three') }}">
<a name="dispatch"></a>
<h3>Dispatch</h3>
<p>{% trans %}Dispatch is a stable, self-hosted IRC client with a web interface. It
has native I2P configuration available by communicating over the{% endtrans %} <a href="{{ site_url('docs/api/samv3') }}">SAM v3 API</a>.</p>
<p>{% trans %}Dispatch is configured with a file called `config.toml`, which you can
configure the common settings.{% endtrans %}</p>
<p>{% trans %} {% endtrans %}</p>
<pre><code>
# Defaults for the client connect form
[defaults]
name = "myinvisibleirc.i2p"
host = "anircservergoeshere.b32.i2p"
port = 6667
channels = [
"#i2p",
"#i2p-dev"
]
server_password = ""
ssl = false
</code></pre>
<a name="servers"></a>
<h2>{% trans %}Servers{% endtrans %}</h2>
<ul>
<li><a href="#eris">Eris(Windows, OSX, Linux)</a></li>
</ul>
<a name="eris"></a>
<h3>Eris</h3>
<p>{% trans %}Eris is an easy-to-configure IRC server with self-configuring support
for I2P. If you want to run a private IRC server it's one of the easiest ways.{% endtrans %}</p>
<p>{% trans %} This is a valid configuration of the Eris IRC server, but it uses a
default password for the admin account(admin). You should change the operator.admin.password
and account.admin.password before deploying to a real service.{% endtrans %}</p>
<pre><code>
mutex: {}
network:
name: Local
server:
password: ""
listen: []
tlslisten: {}
i2plisten:
invisibleirc:
i2pkeys: iirc
samaddr: 127.0.0.1:7656
log: ""
motd: ircd.motd
name: myinvisibleirc.i2p
description: Hidden IRC Services
operator:
admin:
password: JDJhJDA0JE1vZmwxZC9YTXBhZ3RWT2xBbkNwZnV3R2N6VFUwQUI0RUJRVXRBRHliZVVoa0VYMnlIaGsu
account:
admin:
password: JDJhJDA0JGtUU1JVc1JOUy9DbEh1WEdvYVlMdGVnclp6YnA3NDBOZGY1WUZhdTZtRzVmb1VKdXQ5ckZD
www:
listen: []
tlslisten: {}
i2plisten:
i2pinfoirc:
i2pkeys: iircwww
samaddr: "127.0.0.1:7656"
templatedir: lang
</pre></code>
{% endblock %}

7
i2p2www/pages/site/docs/index.html
View File

@@ -1,7 +1,7 @@
{% extends "global/layout.html" %}
{% block title %}{% trans %}Index to Technical Documentation{% endtrans %}{% endblock %}
{% block lastupdated %}2020-08{% endblock %}
{% block accuratefor %}0.9.47{% endblock %}
{% block lastupdated %}2020-11{% endblock %}
{% block accuratefor %}0.9.48{% endblock %}
{% block content %}
<p>{% trans -%}
Following is an index to the technical documentation for I2P.
@@ -158,7 +158,8 @@ Traditionally used only by Java applications and higher-level APIs.
<li><a href="{{ site_url('docs/tunnels/implementation') }}">{{ _('Tunnel building and encryption') }}</a></li>
<li><a href="{{ site_url('docs/how/elgamal-aes') }}">{{ _('ElGamal/AES') }}</a> {{ _('for build request encryption') }}</li>
<li><a href="{{ site_url('docs/how/cryptography') }}">{{ _('ElGamal and AES cryptography details') }}</a></li>
<li><a href="{{ spec_url('tunnel-creation') }}">{{ _('Tunnel building specification') }}</a></li>
<li><a href="{{ spec_url('tunnel-creation') }}">{{ _('Tunnel building specification') }} (ElGamal)</a></li>
<li><a href="{{ spec_url('tunnel-creation-ecies') }}">{{ _('Tunnel building specification') }} (ECIES-X25519)</a></li>
<li><a href="{{ spec_url('tunnel-message') }}">{{ _('Low-level tunnel message specification') }}</a></li>
<li><a href="{{ site_url('docs/tunnels/unidirectional') }}">{{ _('Unidirectional Tunnels') }}</a></li>
<li><a href="{{ url_for('static', filename='pdf/I2P-PET-CON-2009.1.pdf') }}">{{ _('Peer Profiling and Selection in the I2P Anonymous Network') }}</a>

4
i2p2www/spec/ecies.rst
View File

@@ -3,7 +3,7 @@ ECIES-X25519-AEAD-Ratchet
=========================
.. meta::
:category: Protocols
:lastupdated: 2020-09
:lastupdated: 2020-11
:accuratefor: 0.9.47
.. contents::
@@ -131,7 +131,7 @@ Additions to the Framework
``````````````````````````
This specification defines the following enhancements to
Noise_XK_25519_ChaChaPoly_SHA256. These generally follow the guidelines in
Noise_IK_25519_ChaChaPoly_SHA256. These generally follow the guidelines in
[NOISE]_ section 13.
1) Cleartext ephemeral keys are encoded with [Elligator2]_.

38
i2p2www/spec/i2np.rst
View File

@@ -3,7 +3,7 @@ I2NP Specification
==================
.. meta::
:category: Protocols
:lastupdated: 2020-10
:lastupdated: 2020-11
:accuratefor: 0.9.48
.. contents::
@@ -42,6 +42,8 @@ below.
============== ================================================================
Version Required I2NP Features
============== ================================================================
0.9.48 ECIES-X25519 Build Request/Response records
0.9.46 DatabaseLookup flag bit 4 for AEAD reply
0.9.44 X25519 keys in LeaseSet2
@@ -225,16 +227,17 @@ Description
```````````
One Record in a set of multiple records to request the creation of one hop in
the tunnel. For more details see the tunnel overview [TUNNEL-IMPL]_ and the
tunnel creation specification [TUNNEL-CREATION]_.
ElGamal tunnel creation specification [TUNNEL-CREATION]_.
Contents
````````
For ECIES-X25519 BuildRequestRecords, see [TUNNEL-CREATION-ECIES].
Contents (ElGamal)
```````````````````
[TunnelId]_ to receive messages on, followed by the [Hash]_ of our
[RouterIdentity]_. After that the [TunnelId]_ and the [Hash]_ of the next
router's [RouterIdentity]_ follow.
Definition
``````````
ElGamal and AES encrypted:
.. raw:: html
@@ -397,6 +400,18 @@ Notes
BuildResponseRecord
-------------------
Description
```````````
One Record in a set of multiple records with responses to a build request.
For more details see the tunnel overview [TUNNEL-IMPL]_ and the
ElGamal tunnel creation specification [TUNNEL-CREATION]_.
For ECIES-X25519 BuildResponseRecords, see [TUNNEL-CREATION-ECIES].
Contents (ElGamal)
```````````````````
.. raw:: html
{% highlight lang='dataspec' %}
@@ -1412,6 +1427,8 @@ TunnelBuild
Notes
`````
* As of 0.9.48, may also contain ECIES-X25519 BuildRequestRecords, see [TUNNEL-CREATION-ECIES]_.
* See also the tunnel creation specification [TUNNEL-CREATION]_.
* The I2NP message ID for this message must be set according to the tunnel
@@ -1434,6 +1451,8 @@ Same format as `TunnelBuildMessage`, with `BuildResponseRecord`s
Notes
`````
* As of 0.9.48, may also contain ECIES-X25519 BuildResponseRecords, see [TUNNEL-CREATION-ECIES]_.
* See also the tunnel creation specification [TUNNEL-CREATION]_.
* The I2NP message ID for this message must be set according to the tunnel
@@ -1468,6 +1487,8 @@ VariableTunnelBuild
Notes
`````
* As of 0.9.48, may also contain ECIES-X25519 BuildRequestRecords, see [TUNNEL-CREATION-ECIES]_.
* This message was introduced in router version 0.7.12, and may not be sent to
tunnel participants earlier than that version.
@@ -1495,6 +1516,8 @@ VariableTunnelBuildReply
Notes
`````
* As of 0.9.48, may also contain ECIES-X25519 BuildResponseRecords, see [TUNNEL-CREATION-ECIES]_.
* This message was introduced in router version 0.7.12, and may not be sent to
tunnel participants earlier than that version.
@@ -1551,6 +1574,9 @@ References
.. [TUNNEL-CREATION]
{{ spec_url('tunnel-creation') }}
.. [TUNNEL-CREATION-ECIES]
{{ spec_url('tunnel-creation-ecies') }}
.. [TUNNEL-MSG]
{{ spec_url('tunnel-message') }}

4
i2p2www/spec/proposals/144-ecies-x25519-aead-ratchet.rst
View File

@@ -5,7 +5,7 @@ ECIES-X25519-AEAD-Ratchet
:author: zzz, chisana, orignal
:created: 2018-11-22
:thread: http://zzz.i2p/topics/2639
:lastupdated: 2020-05-30
:lastupdated: 2020-11-12
:status: Closed
:target: 0.9.46
:implementedin: 0.9.46
@@ -328,7 +328,7 @@ Additions to the Framework
``````````````````````````
This proposal defines the following enhancements to
Noise_XK_25519_ChaChaPoly_SHA256. These generally follow the guidelines in
Noise_IK_25519_ChaChaPoly_SHA256. These generally follow the guidelines in
[NOISE]_ section 13.
1) Cleartext ephemeral keys are encoded with [Elligator2]_.

5
i2p2www/spec/proposals/152-ecies-tunnels.rst
View File

@@ -6,9 +6,10 @@ ECIES Tunnels
:author: chisana, zzz, orignal
:created: 2019-07-04
:thread: http://zzz.i2p/topics/2737
:lastupdated: 2020-11-05
:status: Open
:lastupdated: 2020-11-16
:status: Closed
:target: 0.9.48
:implementedin: 0.9.48
.. contents::

589
i2p2www/spec/tunnel-creation-ecies.rst Normal file
View File

@@ -0,0 +1,589 @@
=============================
ECIES-X25519 Tunnel Creation
=============================
.. meta::
:category: Protocols
:lastupdated: 2020-11
:accuratefor: 0.9.48
.. contents::
Overview
========
This document specifies Tunnel Build message encryption
using crypto primitives introduced by [ECIES-X25519]_.
It is a portion of the overall proposal
[Prop156]_ for converting routers from ElGamal to ECIES-X25519 keys.
This specification is implemented as of release 0.9.48.
For the purposes of transitioning the network from ElGamal + AES256 to ECIES + ChaCha20,
tunnels with mixed ElGamal and ECIES routers are necessary.
Specifications for handling mixed tunnel hops are provided.
No changes will be made to the format, processing, or encryption of ElGamal hops.
ElGamal tunnel creators will generate ephemeral X25519 keypairs per-hop, and
follow this spec for creating tunnels containing ECIES hops.
This document specifies ECIES-X25519 Tunnel Building.
For an overview of all changes required for ECIES routers, see proposal 156 [Prop156]_.
For additional background on the development of this specification, see proposal 152 [Prop152]_.
This format maintains the same size for tunnel build records,
as required for compatibility. Smaller build records and messages will be
implemented later - see [Prop157]_.
Cryptographic Primitives
------------------------
The primitives required to implement this specification are:
- AES-256-CBC as in [Cryptography]_
- STREAM ChaCha20/Poly1305 functions:
ENCRYPT(k, n, plaintext, ad) and DECRYPT(k, n, ciphertext, ad) - as in [NTCP2]_ [ECIES-X25519]_ and [RFC-7539]_
- X25519 DH functions - as in [NTCP2]_ and [ECIES-X25519]_
- HKDF(salt, ikm, info, n) - as in [NTCP2]_ and [ECIES-X25519]_
Other Noise functions defined elsewhere:
- MixHash(d) - as in [NTCP2]_ and [ECIES-X25519]_
- MixKey(d) - as in [NTCP2]_ and [ECIES-X25519]_
Design
======
Noise Protocol Framework
------------------------
This specification provides the requirements based on the Noise Protocol Framework
[NOISE]_ (Revision 34, 2018-07-11).
In Noise parlance, Alice is the initiator, and Bob is the responder.
It is based on the Noise protocol Noise_N_25519_ChaChaPoly_SHA256.
This Noise protocol uses the following primitives:
- One-Way Handshake Pattern: N
Alice does not transmit her static key to Bob (N)
- DH Function: X25519
X25519 DH with a key length of 32 bytes as specified in [RFC-7748]_.
- Cipher Function: ChaChaPoly
AEAD_CHACHA20_POLY1305 as specified in [RFC-7539]_ section 2.8.
12 byte nonce, with the first 4 bytes set to zero.
Identical to that in [NTCP2]_.
- Hash Function: SHA256
Standard 32-byte hash, already used extensively in I2P.
Handshake Patterns
------------------
Handshakes use [Noise]_ handshake patterns.
The following letter mapping is used:
- e = one-time ephemeral key
- s = static key
- p = message payload
The build request is identical to the Noise N pattern.
This is also identical to the first (Session Request) message in the XK pattern used in [NTCP2]_.
.. raw:: html
{% highlight lang='dataspec' %}
<- s
...
e es p ->
{% endhighlight %}
Request encryption
-----------------------
Build request records are created by the tunnel creator and asymmetrically encrypted to the individual hop.
This asymmetric encryption of request records is currently ElGamal as defined in [Cryptography]_
and contains a SHA-256 checksum. This design is not forward-secret.
The ECIES design uses the one-way Noise pattern "N" with ECIES-X25519 ephemeral-static DH, with an HKDF, and
ChaCha20/Poly1305 AEAD for forward secrecy, integrity, and authentication.
Alice is the tunnel build requestor. Each hop in the tunnel is a Bob.
Reply encryption
-----------------------
Build reply records are created by the hops creator and symmetrically encrypted to the creator.
This symmetric encryption of ElGamal reply records is AES with a prepended SHA-256 checksum.
and contains a SHA-256 checksum. This design is not forward-secret.
ECIES replies use ChaCha20/Poly1305 AEAD for integrity, and authentication.
Specification
=========================
Build Request Records
-------------------------------------
Encrypted BuildRequestRecords are 528 bytes for both ElGamal and ECIES, for compatibility.
Request Record Unencrypted
```````````````````````````````````````
This is the specification of the tunnel BuildRequestRecord for ECIES-X25519 routers.
Summary of changes:
- Remove unused 32-byte router hash
- Change request time from hours to minutes
- Add expiration field for future variable tunnel time
- Add more space for flags
- Add Mapping for additional build options
- AES-256 reply key and IV are not used for the hop's own reply record
- Unencrypted record is longer because there is less encryption overhead
The request record does not contain any ChaCha reply keys.
Those keys are derived from a KDF. See below.
All fields are big-endian.
Unencrypted size: 464 bytes
.. raw:: html
{% highlight lang='dataspec' %}
bytes 0-3: tunnel ID to receive messages as, nonzero
bytes 4-7: next tunnel ID, nonzero
bytes 8-39: next router identity hash
bytes 40-71: AES-256 tunnel layer key
bytes 72-103: AES-256 tunnel IV key
bytes 104-135: AES-256 reply key
bytes 136-151: AES-256 reply IV
byte 152: flags
bytes 153-155: more flags, unused, set to 0 for compatibility
bytes 156-159: request time (in minutes since the epoch, rounded down)
bytes 160-163: request expiration (in seconds since creation)
bytes 164-167: next message ID
bytes 168-x: tunnel build options (Mapping)
bytes x-x: other data as implied by flags or options
bytes x-463: random padding
{% endhighlight %}
The flags field is the same as defined in [Tunnel-Creation]_ and contains the following::
Bit order: 76543210 (bit 7 is MSB)
bit 7: if set, allow messages from anyone
bit 6: if set, allow messages to anyone, and send the reply to the
specified next hop in a Tunnel Build Reply Message
bits 5-0: Undefined, must set to 0 for compatibility with future options
Bit 7 indicates that the hop will be an inbound gateway (IBGW). Bit 6
indicates that the hop will be an outbound endpoint (OBEP). If neither bit is
set, the hop will be an intermediate participant. Both cannot be set at once.
The request exipration is for future variable tunnel duration.
For now, the only supported value is 600 (10 minutes).
The tunnel build options is a Mapping structure as defined in [Common]_.
This is for future use. No options are currently defined.
If the Mapping structure is empty, this is two bytes 0x00 0x00.
The maximum size of the Mapping (including the length field) is 296 bytes,
and the maximum value of the Mapping length field is 294.
Request Record Encrypted
`````````````````````````````````````
All fields are big-endian except for the ephemeral public key which is little-endian.
Encrypted size: 528 bytes
.. raw:: html
{% highlight lang='dataspec' %}
bytes 0-15: Hop's truncated identity hash
bytes 16-47: Sender's ephemeral X25519 public key
bytes 48-511: ChaCha20 encrypted BuildRequestRecord
bytes 512-527: Poly1305 MAC
{% endhighlight %}
Build Reply Records
-------------------------------------
Encrypted BuildReplyRecords are 528 bytes for both ElGamal and ECIES, for compatibility.
Reply Record Unencrypted
`````````````````````````````````````
This is the specification of the tunnel BuildRequestRecord for ECIES-X25519 routers.
Summary of changes:
- Add Mapping for build reply options
- Unencrypted record is longer because there is less encryption overhead
ECIES replies are encrypted with ChaCha20/Poly1305.
All fields are big-endian.
Unencrypted size: 512 bytes
.. raw:: html
{% highlight lang='dataspec' %}
bytes 0-x: Tunnel Build Reply Options (Mapping)
bytes x-x: other data as implied by options
bytes x-510: Random padding
byte 511: Reply byte
{% endhighlight %}
The tunnel build reply options is a Mapping structure as defined in [Common]_.
This is for future use. No options are currently defined.
If the Mapping structure is empty, this is two bytes 0x00 0x00.
The maximum size of the Mapping (including the length field) is 511 bytes,
and the maximum value of the Mapping length field is 509.
The reply byte is one of the following values
as defined in [Tunnel-Creation]_ to avoid fingerprinting:
- 0x00 (accept)
- 30 (TUNNEL_REJECT_BANDWIDTH)
Reply Record Encrypted
```````````````````````````````````
Encrypted size: 528 bytes
.. raw:: html
{% highlight lang='dataspec' %}
bytes 0-511: ChaCha20 encrypted BuildReplyRecord
bytes 512-527: Poly1305 MAC
{% endhighlight %}
After full transition to ECIES records, ranged padding rules are the same as for request records.
Symmetric Encryption of Records
--------------------------------------------------------
Mixed tunnels are allowed, and necessary, for the transition from ElGamal to ECIES.
During the transitionary period, an increasing number of routers will be keyed under ECIES keys.
Symmetric cryptography preprocessing will run in the same way:
- "encryption":
- cipher run in decryption mode
- request records preemptively decrypted in preprocessing (concealing encrypted request records)
- "decryption":
- cipher run in encryption mode
- request records encrypted (revealing next plaintext request record) by participant hops
- ChaCha20 does not have "modes", so it is simply run three times:
- once in preprocessing
- once by the hop
- once on final reply processing
When mixed tunnels are used, tunnel creators will need to base the symmetric encryption
of BuildRequestRecord on the current and previous hop's encryption type.
Each hop will use its own encryption type for encrypting BuildReplyRecords, and the other
records in the VariableTunnelBuildMessage (VTBM).
On the reply path, the endpoint (sender) will need to undo the [Multiple-Encryption]_, using each hop's reply key.
As a clarifying example, let's look at an outbound tunnel w/ ECIES surrounded by ElGamal:
- Sender (OBGW) -> ElGamal (H1) -> ECIES (H2) -> ElGamal (H3)
All BuildRequestRecords are in their encrypted state (using ElGamal or ECIES).
AES256/CBC cipher, when used, is still used for each record, without chaining across multiple records.
Likewise, ChaCha20 will be used to encrypt each record, not streaming across the entire VTBM.
The request records are preprocessed by the Sender (OBGW):
- H3's record is "encrypted" using:
- H2's reply key (ChaCha20)
- H1's reply key (AES256/CBC)
- H2's record is "encrypted" using:
- H1's reply key (AES256/CBC)
- H1's record goes out without symmetric encryption
Only H2 checks the reply encryption flag, and sees its followed by AES256/CBC.
After being processed by each hop, the records are in a "decrypted" state:
- H3's record is "decrypted" using:
- H3's reply key (AES256/CBC)
- H2's record is "decrypted" using:
- H3's reply key (AES256/CBC)
- H2's reply key (ChaCha20-Poly1305)
- H1's record is "decrypted" using:
- H3's reply key (AES256/CBC)
- H2's reply key (ChaCha20)
- H1's reply key (AES256/CBC)
The tunnel creator, a.k.a. Inbound Endpoint (IBEP), postprocesses the reply:
- H3's record is "encrypted" using:
- H3's reply key (AES256/CBC)
- H2's record is "encrypted" using:
- H3's reply key (AES256/CBC)
- H2's reply key (ChaCha20-Poly1305)
- H1's record is "encrypted" using:
- H3's reply key (AES256/CBC)
- H2's reply key (ChaCha20)
- H1's reply key (AES256/CBC)
Request Record Keys
-----------------------------------------------------------------------
These keys are explicitly included in ElGamal BuildRequestRecords.
For ECIES BuildRequestRecords, the tunnel keys and AES reply keys are included,
but the ChaCha reply keys are derived from the DH exchange.
See [Prop156]_ for details of the router static ECIES keys.
Below is a description of how to derive the keys previously transmitted in request records.
KDF for Initial ck and h
````````````````````````
This is standard [NOISE]_ for pattern "N" with a standard protocol name.
.. raw:: html
{% highlight lang='text' %}
This is the "e" message pattern:
// Define protocol_name.
Set protocol_name = "Noise_N_25519_ChaChaPoly_SHA256"
(31 bytes, US-ASCII encoded, no NULL termination).
// Define Hash h = 32 bytes
// Pad to 32 bytes. Do NOT hash it, because it is not more than 32 bytes.
h = protocol_name || 0
Define ck = 32 byte chaining key. Copy the h data to ck.
Set chainKey = h
// MixHash(null prologue)
h = SHA256(h);
// up until here, can all be precalculated by all routers.
{% endhighlight %}
KDF for Request Record
````````````````````````
ElGamal tunnel creators generate an ephemeral X25519 keypair for each
ECIES hop in the tunnel, and use scheme above for encrypting their BuildRequestRecord.
ElGamal tunnel creators will use the scheme prior to this spec for encrypting to ElGamal hops.
ECIES tunnel creators will need to encrypt to each of the ElGamal hop's public key using the
scheme defined in [Tunnel-Creation]_. ECIES tunnel creators will use the above scheme for encrypting
to ECIES hops.
This means that tunnel hops will only see encrypted records from their same encryption type.
For ElGamal and ECIES tunnel creators, they will generate unique ephemeral X25519 keypairs
per-hop for encrypting to ECIES hops.
**IMPORTANT**:
Ephemeral keys must be unique per ECIES hop, and per build record.
Failing to use unique keys opens an attack vector for colluding hops to confirm they are in the same tunnel.
.. raw:: html
{% highlight lang='dataspec' %}
// Each hop's X25519 static keypair (hesk, hepk) from the Router Identity
hesk = GENERATE_PRIVATE()
hepk = DERIVE_PUBLIC(hesk)
// MixHash(hepk)
// || below means append
h = SHA256(h || hepk);
// up until here, can all be precalculated by each router
// for all incoming build requests
// Sender generates an X25519 ephemeral keypair per ECIES hop in the VTBM (sesk, sepk)
sesk = GENERATE_PRIVATE()
sepk = DERIVE_PUBLIC(sesk)
// MixHash(sepk)
h = SHA256(h || sepk);
End of "e" message pattern.
This is the "es" message pattern:
// Noise es
// Sender performs an X25519 DH with Hop's static public key.
// Each Hop, finds the record w/ their truncated identity hash,
// and extracts the Sender's ephemeral key preceding the encrypted record.
sharedSecret = DH(sesk, hepk) = DH(hesk, sepk)
// MixKey(DH())
//[chainKey, k] = MixKey(sharedSecret)
// ChaChaPoly parameters to encrypt/decrypt
keydata = HKDF(chainKey, sharedSecret, "", 64)
// Save for Reply Record KDF
chainKey = keydata[0:31]
// AEAD parameters
k = keydata[32:64]
n = 0
plaintext = 464 byte build request record
ad = h
ciphertext = ENCRYPT(k, n, plaintext, ad)
End of "es" message pattern.
// MixHash(ciphertext)
// Save for Reply Record KDF
h = SHA256(h || ciphertext)
{% endhighlight %}
``replyKey``, ``layerKey`` and ``layerIV`` must still be included inside ElGamal records,
and can be generated randomly.
Reply Record Encryption
--------------------------------------
The reply record is ChaCha20/Poly1305 encrypted.
.. raw:: html
{% highlight lang='dataspec' %}
// AEAD parameters
k = chainkey from build request
n = 0
plaintext = 512 byte build reply record
ad = h from build request
ciphertext = ENCRYPT(k, n, plaintext, ad)
{% endhighlight %}
Implementation Notes
=====================
* Older routers do not check the encryption type of the hop and will send ElGamal-encrypted
records. Some recent routers are buggy and will send various types of malformed records.
Implementers should detect and reject these records prior to the DH operation
if possible, to reduce CPU usage.
References
==========
.. [Common]
{{ spec_url('common-structures') }}
.. [Cryptography]
{{ spec_url('cryptography') }}
.. [ECIES-X25519]
{{ spec_url('ecies') }}
.. [I2NP]
{{ spec_url('i2np') }}
.. [NOISE]
https://noiseprotocol.org/noise.html
.. [NTCP2]
{{ spec_url('ntcp2') }}
.. [Prop119]
{{ proposal_url('119') }}
.. [Prop143]
{{ proposal_url('143') }}
.. [Prop152]
{{ proposal_url('152') }}
.. [Prop153]
{{ proposal_url('153') }}
.. [Prop156]
{{ proposal_url('156') }}
.. [Prop157]
{{ proposal_url('157') }}
.. [Tunnel-Creation]
{{ spec_url('tunnel-creation') }}
.. [Multiple-Encryption]
https://en.wikipedia.org/wiki/Multiple_encryption
.. [RFC-7539]
https://tools.ietf.org/html/rfc7539
.. [RFC-7748]
https://tools.ietf.org/html/rfc7748

BIN
i2p2www/static/images/irc/pidgin-irc-0.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 16 KiB

BIN
i2p2www/static/images/irc/pidgin-irc-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 31 KiB

BIN
i2p2www/static/images/irc/pidgin-irc-2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 42 KiB

BIN
i2p2www/static/images/irc/pidgin-irc-3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 45 KiB

BIN
i2p2www/static/images/irc/revolution-irc-0.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 17 KiB

BIN
i2p2www/static/images/irc/revolution-irc-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 24 KiB

BIN
i2p2www/static/images/irc/revolution-irc-2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB

BIN
i2p2www/static/images/irc/thunderbird-irc-0.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 62 KiB

BIN
i2p2www/static/images/irc/thunderbird-irc-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 30 KiB

BIN
i2p2www/static/images/irc/thunderbird-irc-2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 37 KiB

BIN
i2p2www/static/images/irc/thunderbird-irc-3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 32 KiB

BIN
i2p2www/static/images/irc/thunderbird-irc-4.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 36 KiB

BIN
i2p2www/static/images/irc/thunderbird-irc-5.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 42 KiB

BIN
i2p2www/static/images/irc/thunderbird-irc-6.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

BIN
i2p2www/static/images/irc/tuncheck-irc-all.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 14 KiB

BIN
i2p2www/static/images/irc/xchat-irc-0.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB

BIN
i2p2www/static/images/irc/xchat-irc-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 29 KiB

BIN
i2p2www/static/images/irc/xchat-irc-2.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 59 KiB

BIN
i2p2www/static/images/irc/xchat-irc-3.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 28 KiB

90
i2p2www/translations/fr/LC_MESSAGES/docs.po
View File

@@ -17,7 +17,7 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-12-04 15:24+0000\n"
"PO-Revision-Date: 2020-05-14 18:51+0000\n"
"PO-Revision-Date: 2020-11-04 13:40+0000\n"
"Last-Translator: AO <ao@localizationlab.org>\n"
"Language-Team: French (http://www.transifex.com/otf/I2P/language/fr/)\n"
"Plural-Forms: nplurals=2; plural=(n > 1)\n"
@@ -631,7 +631,7 @@ msgid ""
"emulating\n"
"traditional DNS."
msgstr ""
"Le carnet d’adresses est conduit par web de confiance\n"
"Le carnet d’adresses est conduit par Web de confiance\n"
"sécurisé, distribué, et système de nommage lisible par humain, sacrifiant"
" seulement\n"
"l’appel pour tous les noms lisibles par humain qu’il soient globalement "
@@ -643,7 +643,7 @@ msgstr ""
"pour \"Alice\" qui réfère aux destinations différentes. Les gens peuvent "
"toujours découvrir de nouveaux\n"
"noms en important les carnets d’adresses publiés de pairs indiqués dans "
"leur web de confiance,\n"
"leur Web de confiance,\n"
"ceci en ajoutant les entrées fournies par personne interposée, ou (si "
"quelques personnes organisent\n"
"une série de carnets d’adresses publiés utilisant un système "
@@ -1411,7 +1411,7 @@ msgid ""
"so a user may enter hostnames locally that would be rejected by\n"
"the addressbook subscription rules."
msgstr ""
"Actuellement, les règles d’adressage des carnets d’adresses sont peu "
"Actuellement, les règles d’adréessage des carnets d’adresses sont peu "
"appliquées dans SusiDNS et un utilisateur peut donc saisir localement des"
" noms d’hôtes qui seraient refusés par les règles d’abonnement à des "
"carnets d’adresses."
@@ -2781,7 +2781,7 @@ msgstr "Rendu si l’adresse a été changée"
#: i2p2www/pages/site/docs/api/i2pcontrol.html:95
#: i2p2www/pages/site/docs/api/i2pcontrol.html:96
msgid "Returned if setting was changed"
msgstr "Rendu si l’arrangement a été changé"
msgstr "Rendu si le paramètre a été changé"
#: i2p2www/pages/site/docs/api/i2pcontrol.html:97
msgid "Returns true if any changes were made."
@@ -2937,7 +2937,7 @@ msgid ""
"setting will be returned."
msgstr ""
"Quel port est utilisé pour le transport de TCP. Si nul est soumis, le "
"réglage actuel sera rendu."
"paramètre actuel sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:178
msgid ""
@@ -2945,7 +2945,7 @@ msgid ""
"current setting will be returned."
msgstr ""
"Quel nom d’hôte est utilisé pour le transport de TCP. Si nul est soumis, "
"le réglage courant sera rendu."
"le paramètre courant sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:179
msgid ""
@@ -2953,7 +2953,7 @@ msgid ""
"current setting will be returned."
msgstr ""
"Utilise l’IP détectée automatiquement pour le transport de TCP. Si une "
"valeur nulle est soumise, c’est le réglage actuel sera rendu."
"valeur nulle est soumise, c’est le paramètre actuel sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:180
msgid ""
@@ -2961,7 +2961,7 @@ msgid ""
"setting will be returned."
msgstr ""
"Quel port est utilisé pour le transport d’UDP. Si une valeur nulle est "
"soumise, c’est le réglage actuel qui sera rendu."
"soumise, c’est le paramètre actuel qui sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:181
msgid ""
@@ -2969,7 +2969,7 @@ msgid ""
"current setting will be returned."
msgstr ""
"Quel est lke nom d’hôte utilisé pour le transport d’UDP. Si une valeur "
"nulle est soumise, c’est le réglage actuel qui sera rendu."
"nulle est soumise, c’est le paramètre actuel qui sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:182
msgid ""
@@ -2978,7 +2978,7 @@ msgid ""
msgstr ""
"Quelles sont les méthodes qui devraient être utilisées pour détecter "
"l’adresse IP du transport UDP. Si une valeur nulle est soumise, c’est le "
"réglage actuel qui sera rendu."
"paramètre actuel qui sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:183
msgid "What ip has been detected by the UDP transport."
@@ -2987,7 +2987,7 @@ msgstr "Quelle IP a été détectée par le transport UDP."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:184
msgid "Is UPnP enabled. If null is submitted, current setting will be returned."
msgstr ""
"UPnP est-il permis. Si une valeur nulle est soumise, c’est le réglage "
"UPnP est-il permis. Si une valeur nulle est soumise, c’est le paramètre "
"actuel qui sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:185
@@ -2996,8 +2996,8 @@ msgid ""
"null is submitted, current setting will be returned."
msgstr ""
"Quel est le pourcentage de bande passante utilisable pour des tunnels de "
"participation. Si une valeur nulle est soumise, c’est le réglage courant "
"qui sera rendu."
"participation. Si une valeur nulle est soumise, c’est le paramètre "
"courant qui sera rendu."
#: i2p2www/pages/site/docs/api/i2pcontrol.html:186
msgid ""
@@ -3232,7 +3232,7 @@ msgid ""
"and quick hosting on I2P.\n"
"<br>The document root is:"
msgstr ""
"<b>I2P Webserver</b> – un tunnel pointant vers un serveur web Jetty "
"<b>I2P Webserver</b> – un tunnel pointant vers un serveur Web Jetty "
"exécuté\n"
"sur <a href=\"http://localhost:7658\">localhost:7658</a> pour héberger "
"sur I2P de façon commode et rapide.\n"
@@ -5702,12 +5702,12 @@ msgstr "Serveurs IRC"
#: i2p2www/pages/site/docs/applications/supported.html:58
#: i2p2www/pages/site/docs/applications/supported.html:564
msgid "Web Browsing"
msgstr "Navigation web"
msgstr "Navigation Web"
#: i2p2www/pages/site/docs/applications/supported.html:61
#: i2p2www/pages/site/docs/applications/supported.html:566
msgid "Anonymous websites"
msgstr "Sites web anonymes"
msgstr "Sites Web anonymes"
#: i2p2www/pages/site/docs/applications/supported.html:63
#: i2p2www/pages/site/docs/applications/supported.html:615
@@ -5727,12 +5727,12 @@ msgstr "Mandataires sortants"
#: i2p2www/pages/site/docs/applications/supported.html:72
#: i2p2www/pages/site/docs/applications/supported.html:695
msgid "Website Hosting"
msgstr "Hébergement de site web"
msgstr "Hébergement de site Web"
#: i2p2www/pages/site/docs/applications/supported.html:75
#: i2p2www/pages/site/docs/applications/supported.html:710
msgid "Web servers"
msgstr "Serveurs web"
msgstr "Serveurs Web"
#: i2p2www/pages/site/docs/applications/supported.html:82
#, python-format
@@ -6201,7 +6201,7 @@ msgid ""
"Cache for Gnutella peers on I2P. Website for plugin version\n"
"<a href=\"http://%(stats)s/i2p/plugins/\">here</a>."
msgstr ""
"Cache pour les pairs Gnutella dans I2P. Site web pour la version greffon "
"Cache pour les pairs Gnutella dans I2P. Site Web pour la version greffon "
"<a href=\"http://%(stats)s/i2p/plugins/\">ici</a>."
#: i2p2www/pages/site/docs/applications/supported.html:449
@@ -6345,8 +6345,9 @@ msgid ""
"Privacy-focused non-caching web proxy with advanced filtering\n"
"capabilities. Excels at removing ads and other junk."
msgstr ""
"Mandataire Web sans, cache axé sur la protection des données "
"personnelles, avec des capacités de filtrage évolué. "
"Mandataire Web sans cache axé sur la protection des données personnelles,"
" avec des capacités de filtrage évolué. Particulièrement efficace pour "
"supprimer les publicités et autres nuisances."
#: i2p2www/pages/site/docs/applications/supported.html:635
msgid "Venerable caching web proxy."
@@ -6402,7 +6403,7 @@ msgstr ""
#: i2p2www/pages/site/docs/applications/supported.html:721
msgid "Most popular web server on the public WWW."
msgstr "Serveur web le plus populaire dans le WWW public."
msgstr "Serveur Web le plus populaire dans le WWW public."
#: i2p2www/pages/site/docs/applications/supported.html:727
msgid "Web server and Java servlet container. More features than Jetty."
@@ -6412,7 +6413,7 @@ msgstr ""
#: i2p2www/pages/site/docs/applications/supported.html:733
msgid "Fast lightweight web server."
msgstr "Serveur web poids léger et rapide."
msgstr "Serveur Web poids léger et rapide."
#: i2p2www/pages/site/docs/applications/supported.html:739
msgid "High-performance lightweight web server."
@@ -7825,7 +7826,7 @@ msgstr ""
"cryptographiques (Destinations) et\n"
"peuvent être sensiblement plus gros que des paquets IP. Comme exemples "
"d’utilisation du réseau\n"
"citons les \"eepsites\" (serveurs web hébergeant des applications "
"citons les \"eepsites\" (serveurs Web hébergeant des applications "
"Internet normales au sein d’I2P), un\n"
"client BitTorrent (\"I2PSnark\"), ou un système de stockage distribué. "
"Grâce à l’application\n"
@@ -8202,23 +8203,20 @@ msgid ""
" Machines."
msgstr ""
"Nous sommes une petite <a href=\"%(team)s\">équipe</a> répartie sur "
"plusieurs continents, qui travaille à\n"
"l’avancement\n"
"de différents aspects du projet. Nous sommes complètement ouverts à "
"l’arrivée d’autre développeurs qui voudraient s’impliquer et à celle de "
"quiconque préfèrerait participer d’autres façons, telles que la critique,"
" l’analyse de pair, le test,\n"
"l’écriture d’applications compatibles, ou de documentation. Le système "
"est totalement\n"
"\"open source\" : le routeur et presque tout l’outil de développement "
"sont de plein droit dans le domaine public avec\n"
"quelques lignes de code sous licences BSD et Cryptix, et quelques "
"applications comme I2PTunnel\n"
"et I2PSnark sous GPL. Presque tout est écrit en Java (1.5+), bien que "
"quelques applications de tierce partie soient\n"
"plusieurs continents, qui s’emploie à faire progresser différents aspects"
" du projet. Nous accueillons volontiers d’autres développeurs qui "
"veulent s’impliquer et quiconque voudrait contribuer au projet de "
"différentes manières telles que des critiques, l’évaluation par les "
"pairs, les essais, l’écriture d’applications compatibles avec I2P ou la "
"documentation. Le système est entièrement à code source ouvert; le "
"routeur et la plus grande partie de la trousse de développement logiciel "
"proviennent absolument du domaine public, du code sous licences BSD et "
"Cryptix, alors que certaines applications telles qu’I2PTunnel et I2PSnark"
" sont publiées sous la licence publique générale GNU. Presque tout est "
"écrit en Java (1.5+), bien que certaines applications tierces sont "
"écrites en Python et autres langages. Le code fonctionne sur <a "
"href=\"http://java.com/en/\">Oracle/Sun Java SE</a> et d’autres Machines "
"Virtuelles Java."
"href=\"http://java.com/en/\">Oracle/Sun Java SE</a> et autres machines "
"virtuelles Java."
#: i2p2www/pages/site/docs/how/intro.html:173
msgid "Where?"
@@ -10413,7 +10411,7 @@ msgstr ""
"développement actif depuis le début de 2003 avec un développeur à plein "
"temps et un groupe de collaborateurs consacrés à temps partiel issus du "
"monde entier. Tout le travail fait sur le code source libre d’I2P est "
"librement disponible sur le <a href=\"%(site)s\">site web</a>,\n"
"librement disponible sur le <a href=\"%(site)s\">site Web</a>,\n"
"avec la majorité du code sorti sans réserve dans le domaine public, "
"quoique \n"
"faisant usage de quelques routines de chiffrement conformément sous "
@@ -12256,7 +12254,7 @@ msgstr ""
"Internet. Au lieu de cela, nous travaillons à fournir de l’anonymat "
"suffisant pour répondre aux\n"
"besoins réels de quiconque nous pouvons - de ceux naviguant simplement "
"sur des sites web, à ceux échangeant des données, à ceux craintifs d’être"
"sur des sites Web, à ceux échangeant des données, à ceux craintifs d’être"
" découverts par organisations puissantes ou états."
#: i2p2www/pages/site/docs/how/threat-model.html:82
@@ -13399,8 +13397,8 @@ msgstr ""
" version 0.6.1.31, avec des améliorations supplémentaires dans les "
"versions suivantes.\n"
"Cependant, tout service de noms exige un certain degré de confiance. "
"Consulter <a href=\"%(naming)s\">la page sur l’adressage</a> pour plus de"
" précisions."
"Consulter <a href=\"%(naming)s\">la page sur l’adréessage</a> pour plus "
"de précisions."
#: i2p2www/pages/site/docs/how/threat-model.html:869
msgid ""
@@ -14972,7 +14970,7 @@ msgid ""
"IP: Internet Protocol, allow addressing hosts on the regular internet and"
" routing packets across the internet using best-effort delivery."
msgstr ""
"IP : Protocole Internet, permet l’adressage d’hôtes sur l’Internet "
"IP : Protocole Internet, permet l’adréessage d’hôtes sur l’Internet "
"ordinaire et le routage de paquets par Internet en utilisant la livraison"
" au mieux."

54
i2p2www/translations/fr/LC_MESSAGES/get-involved.po
View File

@@ -7,6 +7,7 @@
# AO <ao@localizationlab.org>, 2018-2020
# Boxoa590, 2013
# AO <ao@localizationlab.org>, 2017-2018
# . ., 2020
# magma <magma@mail.i2p>, 2011
# 88debc4075076105339fa4916a2f6c30, 2016
# syl_, 2013,2015-2016
@@ -17,7 +18,7 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-11-24 14:26+0000\n"
"PO-Revision-Date: 2020-04-16 21:11+0000\n"
"PO-Revision-Date: 2020-10-06 19:24+0000\n"
"Last-Translator: AO <ao@localizationlab.org>\n"
"Language-Team: French (http://www.transifex.com/otf/I2P/language/fr/)\n"
"Plural-Forms: nplurals=2; plural=(n > 1)\n"
@@ -85,23 +86,23 @@ msgstr ""
#: i2p2www/pages/site/get-involved/donate.html:35
msgid "BTC Address"
msgstr ""
msgstr "Adresse BTC"
#: i2p2www/pages/site/get-involved/donate.html:37
msgid "LTC Address"
msgstr ""
msgstr "Adresse LTC"
#: i2p2www/pages/site/get-involved/donate.html:39
msgid "ETH Address"
msgstr ""
msgstr "Adresse ETH"
#: i2p2www/pages/site/get-involved/donate.html:41
msgid "ANC Address"
msgstr ""
msgstr "Adresse ANC"
#: i2p2www/pages/site/get-involved/donate.html:43
msgid "XMR Address"
msgstr ""
msgstr "Adresse XMR"
#: i2p2www/pages/site/get-involved/donate.html:45
msgid "We now also accept paypal donations!"
@@ -126,11 +127,11 @@ msgstr ""
#: i2p2www/pages/site/get-involved/donate.html:71
msgid "E-mail: "
msgstr ""
msgstr "Adresse courriel :"
#: i2p2www/pages/site/get-involved/donate.html:72
msgid "Message: "
msgstr ""
msgstr "Message :"
#: i2p2www/pages/site/get-involved/donate.html:78
msgid "Tax Status"
@@ -870,7 +871,7 @@ msgstr ""
"vous pouvez utiliser des applications classiques sans avoir besoin de "
"programmer un support explicite à I2P.\n"
"Ceci est très efficace pour un scénario client-serveur,\n"
"où vous avez besoin de vous connecter à un simple site web.\n"
"où vous avez besoin de vous connecter à un simple site Web.\n"
"Vous pouvez simplement créer un tunnel utilisant I2PTunnel pour connecter"
" à ce site Web, comme indiqué dans <a "
"href=\"#tunnel.serverclient\">Figure 1</a>."
@@ -902,10 +903,10 @@ msgstr ""
"d’instances I2PTunnel augmente grandement la surcharge.\n"
"De plus, avec de nombreux protocoles vous devrez forcer tout le monde à "
"utiliser le même jeu de ports pour tous les pairs - par exemple si vous "
"voulez exécuter de façon fiable des conversations DCC, tout le monde doit"
" accepter que le port 10001 soit Alice, le port 10002 soit Bob, le port "
"10003 soit Charlie et ainsi de suite, puisque le protocole inclut des "
"informations spécifiques TCP/IP (hôte et port)."
"souhaitez exécuter de façon fiable des conversations DCC, tout le monde "
"doit accepter que le port 10001 soit Alice, le port 10002 soit Bob, le "
"port 10003 soit Charlie et ainsi de suite, puisque le protocole inclut "
"des informations spécifiques TCP/IP (hôte et port)."
#: i2p2www/pages/site/get-involved/develop/applications.html:36
msgid ""
@@ -1523,7 +1524,7 @@ msgid ""
"server instead is straightforward.\n"
"Any standard web app technology should work."
msgstr ""
"I2P arrive avec le serveur web Jetty, et au lieu de cela vous pouvez "
"I2P arrive avec le serveur Web Jetty, et au lieu de cela vous pouvez "
"directement configurer I2P pour utiliser le serveur Apache.\n"
"N’importe quelle technologie d’application Web standard devrait marcher."
@@ -3227,7 +3228,7 @@ msgstr ""
"Si vous avez seulement l’intention de récupérer le code depuis MTN, "
"n’hésitez pas à sauter jusqu’à la\n"
"<a href=\"#trust-and-initializing-your-repository\">section suivante</a>."
" Si vous voulez\n"
" Si vous souhaitez\n"
"générer des clés, lisez la suite."
#: i2p2www/pages/site/get-involved/guides/monotone.html:100
@@ -3504,11 +3505,11 @@ msgstr ""
#: i2p2www/pages/site/get-involved/guides/monotone.html:283
msgid "If you only want I2P sources:"
msgstr "Si vous voulez seulement des sources d’I2P :"
msgstr "Si vous souhaitez seulement des sources d’I2P :"
#: i2p2www/pages/site/get-involved/guides/monotone.html:292
msgid "If you want all branches:"
msgstr "Si vous voulez toutes les branches :"
msgstr "Si vous souhaitez toutes les branches :"
#: i2p2www/pages/site/get-involved/guides/monotone.html:298
msgid ""
@@ -3844,7 +3845,7 @@ msgstr ""
"\n"
"Donc vous voulez commencer à travailler sur I2P ? Très bien !\n"
"Voici un guide rapide pour commencer\n"
"en contribuant au site web ou au logiciel, faire du développement ou "
"en contribuant au site Web ou au logiciel, faire du développement ou "
"créer des traductions."
#: i2p2www/pages/site/get-involved/guides/new-developers.html:27
@@ -3957,8 +3958,9 @@ msgid ""
"If you want to remain anonymous, you need to do an additional step, to "
"set up a connection to a monotone server over I2P:"
msgstr ""
"Si vous voulez rester anonyme, vous devez faire une étape supplémentaire,"
" pour configurer une connexion à un serveur Monotone au travers d’I2P :"
"Si vous souhaitez rester anonyme, vous devez faire une étape "
"supplémentaire, pour configurer une connexion à un serveur Monotone au "
"travers d’I2P :"
#: i2p2www/pages/site/get-involved/guides/new-developers.html:87
#, python-format
@@ -4041,7 +4043,7 @@ msgid ""
"'i2p.www' instead of 'i2p.i2p'."
msgstr ""
"\n"
"Pour télécharger les fichiers du site web à la place des fichiers source "
"Pour télécharger les fichiers du site Web à la place des fichiers source "
"d’I2P, utiliser 'i2p.www' à la place de 'i2p.i2p'."
#: i2p2www/pages/site/get-involved/guides/new-developers.html:124
@@ -4125,7 +4127,7 @@ msgid ""
msgstr ""
"Voir la <a href=\"http://%(zzz)s/forums/3\">liste de zzz de TODO (choses "
"à faire)</a>,\n"
"<a href=\"%(todo)s\">liste TODO concernant ce site web</a> ou\n"
"<a href=\"%(todo)s\">liste TODO concernant ce site Web</a> ou\n"
"<a href=\"%(trac)s\">Trac</a>\n"
"pour des idées."
@@ -4140,7 +4142,7 @@ msgstr ""
"Voyez en bas de <a href=\"%(licenses)s#commit\">la page licences</a> pour"
"\n"
"les exigences de privilège d’engagement. Vous avez besoin de ceux-ci pour"
" mettre du code dans i2p.i2p (non exigé pour le site web !)."
" mettre du code dans i2p.i2p (non exigé pour le site Web !)."
#: i2p2www/pages/site/get-involved/guides/new-developers.html:172
msgid "Short version of how to generate and use keys if you plan to commit:"
@@ -4263,7 +4265,7 @@ msgstr "Voici un guide très rapide pour débuter."
#: i2p2www/pages/site/get-involved/guides/new-translators.html:6
msgid "How to Translate the Website"
msgstr "Comment traduire le site web"
msgstr "Comment traduire le site Web"
#: i2p2www/pages/site/get-involved/guides/new-translators.html:8
#, python-format
@@ -4440,7 +4442,7 @@ msgid ""
"At least an i2p homepage in your language would be great."
msgstr ""
"Avant le départ d’une traduction de la console, il est mieux de traduire "
"d’abord quelques pages web I2P.\n"
"d’abord quelques pages Web I2P.\n"
"Au minimum une page d’accueil I2P dans votre langue serait super."
#: i2p2www/pages/site/get-involved/guides/new-translators.html:106
@@ -4688,7 +4690,7 @@ msgid ""
" The complexities include:"
msgstr ""
"Dans sa forme la plus simple, un serveur de réensemencement consiste en "
"un routeur I2P Java, un serveur web HTTP,\n"
"un routeur I2P Java, un serveur Web HTTP,\n"
"et quelques scripts qui collectent périodiquement des infos de routeurs à"
" partir du routeur,\n"
"les groupant et les signant dans un format de fichier personnalisé et "

19
i2p2www/translations/fr/LC_MESSAGES/priority.po
View File

@@ -19,7 +19,7 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-12-04 15:24+0000\n"
"PO-Revision-Date: 2020-04-18 11:49+0000\n"
"PO-Revision-Date: 2020-10-07 20:40+0000\n"
"Last-Translator: AO <ao@localizationlab.org>\n"
"Language-Team: French (http://www.transifex.com/otf/I2P/language/fr/)\n"
"Plural-Forms: nplurals=2; plural=(n > 1)\n"
@@ -190,8 +190,8 @@ msgid ""
"Once Synaptic opens, select <em>Repositories</em> from the "
"<em>Settings</em> menu."
msgstr ""
"Une fois Synaptic ouvert, sélectionner <em>Dépôts</em> dans le menu "
"<em>Configuration</em>."
"Une fois Synaptic ouvert, sélectionnez <em>Dépôts</em> dans le menu "
"<em>Paramètres</em>."
#: i2p2www/pages/downloads/debian.html:71
msgid ""
@@ -425,8 +425,8 @@ msgid ""
"href=\"%(browserconfig)s\">browser proxy setup</a> page for an easy "
"howto."
msgstr ""
"Si vous voulez atteindre des sites eep avec votre navigateur, un guide "
"pratique facile se trouve sur la page <a href=\"%(browserconfig)s\">de "
"Si vous souhaitez atteindre des sites eep avec votre navigateur, un guide"
" pratique facile se trouve sur la page <a href=\"%(browserconfig)s\">de "
"configuration du mandataire des navigateurs</a>."
#: i2p2www/pages/downloads/firefox.html:5 i2p2www/pages/downloads/list.html:72
@@ -1139,7 +1139,7 @@ msgstr "500 Erreur serveur"
#: i2p2www/pages/global/error_500.html:17
msgid "Umm... the server encountered some sort of error."
msgstr "Hum ! Le serveur a rencontré quelque erreur."
msgstr "Hum ! Une erreur de serveur est survenue."
#: i2p2www/pages/global/footer.html:4 i2p2www/pages/global/nav.html:9
msgid "FAQ"
@@ -1545,7 +1545,7 @@ msgid ""
"<a href=\"%(blogindex)s\">Status updates</a> from developers are also "
"available."
msgstr ""
"Si vous voulez discuter de quelque chose, veuillez vous adresser aux "
"Si vous souhaitez discuter de quelque chose, veuillez vous adresser aux "
"développeurs sur IRC dans #I2P-dev. \n"
"<a href=\"%(blogindex)s\">Les mises à jour d’état</a> des développeurs "
"sont également à disposition."
@@ -3565,8 +3565,9 @@ msgstr ""
"disponible, ce qui à son tour améliore votre expérience sur I2P.\n"
"Les paramètres de bande passante se trouvent sur la page <a "
"href=\"http://localhost:7657/config\">http://localhost:7657/config.</a>\n"
"Veuillez garder à l’esprit les limites de votre connexion Internet telles"
" que déterminées par votre FAI et ajuster vos paramètres en conséquence."
"Veuillez garder à l’esprit les limites de votre connexion à Internet "
"telles que déterminées par votre FAI et ajuster vos paramètres en "
"conséquence."
#: i2p2www/pages/site/faq.html:893
msgid ""

6
i2p2www/translations/ko/LC_MESSAGES/comparison.po
View File

@@ -9,8 +9,8 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-08-24 11:47+0000\n"
"PO-Revision-Date: 2018-10-04 00:31+0000\n"
"Last-Translator: erinm\n"
"PO-Revision-Date: 2020-11-04 00:06+0000\n"
"Last-Translator: ylsun <y15un@y15un.dog>\n"
"Language-Team: Korean (http://www.transifex.com/otf/I2P/language/ko/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
"MIME-Version: 1.0\n"
@@ -296,7 +296,7 @@ msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:254
msgid "Others"
msgstr ""
msgstr "기타 사항"
#: i2p2www/pages/site/comparison/tor.html:2
msgid "I2P Compared to Tor"

75
i2p2www/translations/ko/LC_MESSAGES/docs.po
View File

@@ -7,9 +7,9 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-08-24 16:39+0000\n"
"PO-Revision-Date: 2019-10-02 10:29+0000\n"
"Last-Translator: Giovanni Pellerano <giovanni.pellerano@evilaliv3.org>\n"
"POT-Creation-Date: 2019-12-04 15:24+0000\n"
"PO-Revision-Date: 2020-11-02 11:35+0000\n"
"Last-Translator: 장민준 <mizizang@gmail.com>\n"
"Language-Team: Korean (http://www.transifex.com/otf/I2P/language/ko/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
"MIME-Version: 1.0\n"
@@ -551,7 +551,6 @@ msgid "not current"
msgstr ""
#: i2p2www/pages/site/docs/naming.html:3 i2p2www/pages/site/docs/api/bob.html:3
#: i2p2www/pages/site/docs/protocol/i2cp.html:3
msgid "June 2019"
msgstr ""
@@ -1304,7 +1303,7 @@ msgstr ""
#: i2p2www/pages/site/docs/plugins.html:100
msgid "Installation"
msgstr ""
msgstr "설치"
#: i2p2www/pages/site/docs/plugins.html:101
msgid ""
@@ -1465,7 +1464,7 @@ msgid ""
"in the 767x range."
msgstr ""
#: i2p2www/pages/site/docs/ports.html:57
#: i2p2www/pages/site/docs/ports.html:59
msgid "recommended spot for new plugins/applications"
msgstr ""
@@ -4257,10 +4256,6 @@ msgstr ""
msgid "Embedding I2P in your Application"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:3
msgid "November 2017"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:8
msgid ""
"This page is about bundling the entire I2P router binary with your "
@@ -4593,55 +4588,57 @@ msgid ""
"Some apps may need more, e.g. i2ptunnel.jar or addressbook.jar.\n"
"Don't forget jbigi.jar, or a subset of it for the platforms you support, "
"to make the crypto much faster.\n"
"We are currently building them for Java 7, as of 0.9.24. The source is "
"mostly compatible with Java 6 if you want to do your own compile,\n"
"but we may start using Java 7 features at any time without notice.\n"
"Java 7 or higher is required to build.\n"
"If you're building Debian / Ubuntu packages, you should require the I2P "
"package from our PPA instead of bundling it.\n"
"You almost certainly do not need susimail, susidns, the router console, "
"and i2psnark, for example."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:229
#: i2p2www/pages/site/docs/applications/embedding.html:228
msgid ""
"The following files should be included in the I2P installation directory,"
" specified with the \"i2p.dir.base\" property.\n"
"Don't forget certificates/reseed and certificates/ssl, required for "
"Don't forget the certificates/ directory, which is required for "
"reseeding, and blocklist.txt for IP validation.\n"
"The geoip directory is optional, but recommended so the router can make "
"decisions based on location.\n"
"If including geoip, be sure to put the file GeoLite2-Country.mmdb in that"
" directory (gunzip it from installer/resources/GeoLite2-Country.mmdb.gz)."
"\n"
"The hosts.txt file may be necessary, you may modify it to include any "
"hosts your application uses.\n"
"You may add a router.config file to the base directory to override "
"initial defaults."
"initial defaults.\n"
"Review and edit or remove the clients.config and i2ptunnel.config files."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:236
#: i2p2www/pages/site/docs/applications/embedding.html:237
msgid ""
"License requirements may require you to include the LICENSES.txt file and"
" the licenses directory."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:242
#: i2p2www/pages/site/docs/applications/embedding.html:243
msgid "You may also wish to bundle a hosts.txt file."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:245
#: i2p2www/pages/site/docs/applications/embedding.html:246
msgid "Be sure to specify a Java 7 bootclasspath if compiling with Java 8."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:253
#: i2p2www/pages/site/docs/applications/embedding.html:254
msgid "Android considerations"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:254
#: i2p2www/pages/site/docs/applications/embedding.html:255
msgid ""
"Our Android router app may be shared by multiple clients.\n"
"If it is not installed, the user will be prompted when he starts a client"
" app."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:258
#: i2p2www/pages/site/docs/applications/embedding.html:259
msgid ""
"Some developers have expressed concern that this is a poor user "
"experience,\n"
@@ -4651,16 +4648,16 @@ msgid ""
"More information needed."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:264
#: i2p2www/pages/site/docs/applications/embedding.html:275
#: i2p2www/pages/site/docs/applications/embedding.html:265
#: i2p2www/pages/site/docs/applications/embedding.html:276
msgid "If you require assistance, please contact us."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:270
#: i2p2www/pages/site/docs/applications/embedding.html:271
msgid "Maven jars"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:271
#: i2p2www/pages/site/docs/applications/embedding.html:272
msgid ""
"We have a limited number of our jars on <a "
"href=\"http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22net.i2p%22\">Maven"
@@ -4669,11 +4666,11 @@ msgid ""
"expand the released jars on Maven Central."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:281
#: i2p2www/pages/site/docs/applications/embedding.html:282
msgid "Datagram (DHT) considerations"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:282
#: i2p2www/pages/site/docs/applications/embedding.html:283
msgid ""
"If your application is using I2P datagrams, e.g. for a DHT,\n"
"there's lots of advanced options available to reduce overhead and "
@@ -4689,32 +4686,32 @@ msgid ""
"have several."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:295
#: i2p2www/pages/site/docs/applications/embedding.html:296
msgid "Comarketing"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:296
#: i2p2www/pages/site/docs/applications/embedding.html:297
msgid ""
"Let's work together. Don't wait until it's done.\n"
"Give us your Twitter handle and start tweeting about it, we will return "
"the favor."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:302
#: i2p2www/pages/site/docs/applications/embedding.html:303
msgid "Malware"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:303
#: i2p2www/pages/site/docs/applications/embedding.html:304
msgid ""
"Please don't use I2P for evil.\n"
"It could cause great harm both to our network and our reputation."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:309
#: i2p2www/pages/site/docs/applications/embedding.html:310
msgid "Join Us"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:310
#: i2p2www/pages/site/docs/applications/embedding.html:311
msgid ""
"This may be obvious, but join the community. Run I2P 24/7. Start an "
"eepsite about your project.\n"
@@ -4722,11 +4719,11 @@ msgid ""
"We can help get you users, testers, translators, or even coders."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:318
#: i2p2www/pages/site/docs/applications/embedding.html:319
msgid "Application Examples"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:319
#: i2p2www/pages/site/docs/applications/embedding.html:320
msgid ""
"You may wish to install and play with the I2P Android app, and look at "
"its code, for an example of an application that bundles the router.\n"
@@ -4736,17 +4733,17 @@ msgid ""
" and Monero."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:327
#: i2p2www/pages/site/docs/applications/embedding.html:328
msgid "Code Example"
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:328
#: i2p2www/pages/site/docs/applications/embedding.html:329
msgid ""
"None of the above actually tells you how to write your code to\n"
"bundle the Java router, so following is a brief example."
msgstr ""
#: i2p2www/pages/site/docs/applications/embedding.html:358
#: i2p2www/pages/site/docs/applications/embedding.html:359
msgid ""
"This code is for the case where your application starts the router, as in"
" our Android app.\n"

6
i2p2www/translations/ko/LC_MESSAGES/get-involved.po
View File

@@ -8,8 +8,8 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-11-24 14:26+0000\n"
"PO-Revision-Date: 2019-11-26 08:54+0000\n"
"Last-Translator: Johnny Cho <popeye92@gmail.com>\n"
"PO-Revision-Date: 2020-11-04 00:06+0000\n"
"Last-Translator: ylsun <y15un@y15un.dog>\n"
"Language-Team: Korean (http://www.transifex.com/otf/I2P/language/ko/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
"MIME-Version: 1.0\n"
@@ -1666,7 +1666,7 @@ msgstr ""
#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14
#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169
msgid "Others"
msgstr ""
msgstr "기타 사항"
#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17
msgid ""

991
i2p2www/translations/pl/LC_MESSAGES/priority.po
View File

File diff suppressed because it is too large Load Diff

322
i2p2www/translations/ru/LC_MESSAGES/about.po
View File

@@ -4,30 +4,31 @@
#
# Translators:
# Aleksey Orekhov <opexob@yandex.ru>, 2013
# Алексей Выскубов <viskubov@gmail.com>, 2016
# Alexander Georgievskiy <galeksandrp@gmail.com>, 2017
# Aleksey Vyskubov <viskubov@gmail.com>, 2016
# Alexander Georgievskiy <galeksandrp@gmail.com>, 2017,2020
# Arthur Siyatelev <u235xc@gmail.com>, 2013
# Petr Polyakov, 2014
# dimi <zhopa@mita.pp.ru>, 2013
# Dmitriy Mamonov <sassy.but.classic@gmail.com>, 2013
# Evgeny Lavrov <EvgenyLavrov@gmail.com>, 2019
# Alexander Georgievskiy <galeksandrp@gmail.com>, 2016
# Irina Fedulova <istartlin@gmail.com>, 2020
# Maxym Mykhalchuk, 2014
# Jaime Hayes, 2013
# 7124aed30012f02d27095ba0a6fa9da4_e31a9a3, 2013
# Nikita <Terexnik@gmail.com>, 2013
# Nikolay Parukhin <parukhin@gmail.com>, 2014,2018
# Oleg Sergeev <djvnsk@ya.ru>, 2015
# R4SAS, 2019
# vertnis, 2015
# vertnis, 2015,2019
# yume, 2014-2015
# yume, 2016,2018
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-08-24 16:39+0000\n"
"PO-Revision-Date: 2019-08-24 16:43+0000\n"
"Last-Translator: zzzi2p\n"
"POT-Creation-Date: 2019-12-04 15:24+0000\n"
"PO-Revision-Date: 2020-10-26 18:35+0000\n"
"Last-Translator: Alexander Georgievskiy <galeksandrp@gmail.com>\n"
"Language-Team: Russian (Russia) "
"(http://www.transifex.com/otf/I2P/language/ru_RU/)\n"
"Plural-Forms: nplurals=4; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && "
@@ -114,8 +115,8 @@ msgid ""
"<a href='%(profile)s'>Firefox profile</a>."
msgstr ""
"Если вы используете Windows, рекомендуемый метод получения доступа в I2P "
"используя \n"
"<a href='%(profile)s'>профиль для Firefox</a>."
"- это использование \n"
"<a href='%(profile)s'>профиля для Firefox</a>."
#: i2p2www/pages/site/about/browser-config.html:16
msgid ""
@@ -172,7 +173,7 @@ msgstr ""
"Установите флажок напротив \"Использовать прокси-сервер для локальных "
"подключений\" и \"Не использовать прокси-сервер для локальных адресов\". "
"Нажмите кнопку Дополнительно для ввода отдельных адресов прокси. "
"Установите значения, как на картинке: IP 127.0.0.1 и порт 4444 для HTTP, "
"Установите значения как на картинке: IP 127.0.0.1 и порт 4444 для HTTP, "
"порт 4445 для HTTPS. Сохраните настройки нажатием на OK, теперь ваш "
"браузер настроен для использования I2P прокси.\n"
"<b>Примечание:</b> в целях приватности установите для FTP-прокси те же "
@@ -239,7 +240,7 @@ msgstr ""
"В меню Настройки выберите пункт Опции, чтобы открыть панель настроек "
"Firefox. Нажмите на иконку с названием <em>Дополнительно</em>, затем "
"нажмите на закладку <em>Сеть</em>. В секции <em>Соединение</em>, нажмите "
"кнопку Настройки. Вы увидите окно как показано ниже:"
"кнопку Настройки. Вы увидите окно, как показано ниже:"
#: i2p2www/pages/site/about/browser-config.html:76
msgid "Firefox Network Options"
@@ -259,7 +260,7 @@ msgstr ""
"В <em>Настройках Соединения</em> выберите <em>Настраивать прокси "
"вручную</em>, затем введите 127.0.0.1, порт 4444 в поле HTTP-прокси. "
"Введите 127.0.0.1, порт 4445 в поле SSL-прокси.\n"
"Убедитесь, что вы ввели localhost и 127.0.0.1 в тесктовом поле \"Не "
"Убедитесь, что вы ввели localhost и 127.0.0.1 в текстовом поле \"Не "
"использовать прокси для\".\n"
"<b>Примечание:</b> в целях приватности установите для FTP-прокси те же "
"параметры, что и для HTTP-прокси. "
@@ -295,8 +296,8 @@ msgid ""
"<b>Note/Privacy tip:</b> Set the FTP proxy to the same settings as the "
"HTTP proxy."
msgstr ""
"Введите 127.0.0.1 и портt 4444 в поле HTTP. Введите 127.0.0.1 и порт 4445"
" в поле\n"
"Введите 127.0.0.1 и порт 4444 в поле HTTP. Введите 127.0.0.1 и порт 4445 "
"в поле\n"
"HTTPS. Введите <code>127.0.0.1,localhost</code> в поле Исключения. "
"Нажмите Принять, затем OK \n"
"для закрытия окна настроек.\n"
@@ -310,7 +311,7 @@ msgid ""
"Instead, it is meant to be used as an internal network."
msgstr ""
"Помните: I2P не был спроектирован для создания прокси во внешний "
"Интернет.\n"
"интернет.\n"
"Вместо этого I2P предназначена для использования в качестве внутренней "
"сети."
@@ -370,7 +371,7 @@ msgid ""
"outproxy to the Internet."
msgstr ""
"<a href=\"https://www.torproject.org\">Tor</a> - хорошее приложение для "
"использования в качестве внешнего прокси в Интернет. "
"использования в качестве внешнего прокси в интернете. "
#: i2p2www/pages/site/about/glossary.html:2
msgid "Glossary"
@@ -399,6 +400,14 @@ msgid ""
"currently. Here we do track those who gave us a name to be published in a"
" I2P hall of fame."
msgstr ""
"Проект I2P целиком сделан энтузиастами в их свободное время. Однако "
"крупный проект, такой как\n"
"I2P не состоит только из программ; для получения выдающихся результатов\n"
"может потребоваться зарегистрировать доменов, оплатить кофе и несколько "
"серверов. Люди со всего мира осуществляли пожертвования на I2P, чтобы он "
"достиг нынешнего\n"
"вида. Здесь мы указываем тех, кто сообщил свое имя для упоминания на "
"аллее славы I2P."
#: i2p2www/pages/site/about/hall-of-fame.html:12
msgid "Big thanks go to the following people who have donated to I2P!"
@@ -411,16 +420,18 @@ msgid ""
"href=\"mailto:%(echelon)s\">echelon</a>\n"
"with your name or nick (and optionally homepage) so we can list you here."
msgstr ""
"Если вы сделали пожертвование, пожалуйста, пошлите email на <a "
"Если вы сделали пожертвование, пожалуйста, отправьте email на <a "
"href=\"mailto:%(echelon)s\">echelon</a>\n"
"с вашим именем или ником (и, по желанию, домашней страницей), чтобы мы "
"смогли указать вас здесь."
#: i2p2www/pages/site/about/hall-of-fame.html:18
msgid ""
"The unsorted list of I2P donors in 15 years of I2P history,starting march"
" 2004 til march 2019."
"The unsorted list of I2P donors in 15 years of I2P history, starting "
"March 2004 til March 2019."
msgstr ""
"Несортированный список доноров I2P за 15 лет истории I2P, начиная с марта"
" 2004 года по март 2019 года."
#: i2p2www/pages/site/about/intro.html:2
msgid "Intro"
@@ -506,7 +517,7 @@ msgstr ""
"количество пиров, ретранслирующих каждое сообщение из конца в конец,\n"
"сведено к абсолютному минимуму, необходимому, чтобы удовлетворить\n"
"\"модель угрозы\" (уровень желаемой безопасности) как отправителя, так и "
"получателя. "
"получателя."
#: i2p2www/pages/site/about/intro.html:34
#, python-format
@@ -562,7 +573,8 @@ msgstr ""
"I2P, а те, что обычно используют TCP, могут использовать TCP-подобную \n"
"потоковую библиотеку. У нас есть приложение общего TCP/IP моста\n"
"(\"<a href=\"%(i2ptunnel)s\">I2PTunnel</a>\"), которое позволяет людям \n"
"пересылать TCP потоки в I2P сеть также как получать потоки извне сети и \n"
"пересылать TCP потоки в I2P сеть так же, как и получать потоки извне сети"
" и \n"
"пересылать их на определённый TCP/IP адрес."
#: i2p2www/pages/site/about/intro.html:63
@@ -602,8 +614,8 @@ msgstr ""
"href=\"%(bittorrent)s\">BitTorrent</a>), распределенным хранилищем данных"
" (а-ля <a href=\"%(freenet)s\">Freenet</a> / <a "
"href=\"%(mnet)s\">MNet</a>) и системой блогов (полностью распределенным "
"аналогом <a href=\"%(livejournal)s\">LiveJournal</a>), но в данный момент"
" они ещё не готовы к использованию. "
"аналогом <a href=\"%(livejournal)s\">LiveJournal</a>), но на данный "
"момент они ещё не готовы к использованию. "
#: i2p2www/pages/site/about/intro.html:82
#, python-format
@@ -630,11 +642,11 @@ msgid ""
"certain circumstances the technique could be appropriate."
msgstr ""
"По своей сути I2P не является сетью для доступа во \"внешний Интернет\" -"
" тот, кому Вы посылаете сообщение представлен криптографическим "
" тот, кому вы посылаете сообщение, представлен криптографическим "
"идентификатором, а не каким-либо IP-адресом, поэтому сообщение должно "
"быть адресовано кому-то, у кого запущен I2P. Тем не менее вполне "
"возможно, что тот пользователь предоставляет внешний прокси, позволяя Вам"
" анонимно использовать своё Интернет соединение. Для примера, "
"быть адресовано кому-то, у кого запущен I2P. Тем не менее, вполне "
"возможно, что тот пользователь предоставляет внешний прокси, позволяя вам"
" анонимно использовать своё интернет-соединение. Для примера, "
"\"eepproxy\" обрабатывает не-I2P адреса (например, "
"\"http://www.i2p.net\") и направляет их по определённому адресу, на "
"котором запущен HTTP-прокси <a href=\"%(squid)s\">squid</a>, "
@@ -668,14 +680,14 @@ msgid ""
"our schedule."
msgstr ""
"<a href=\"%(team)s\">Команда</a> разработчиков I2P - это группа, открытая"
" для всех кто заинтересован <a href=\"%(volunteer)s\">принять "
" для всех, кто заинтересован <a href=\"%(volunteer)s\">принять "
"участие</a>, и весь код проекта - это <a href=\"%(licenses)s\">открытый "
"код</a>. Ядро I2P SDK и текущая реализация роутера выполнены на языке "
"Java (в настоящий момент поддерживаются реализации от sun и kaffe, "
"реализация поддержки gcj запланирована на будущее), также существует <a "
"href=\"%(sam)s\">простое основанное на сокетах API</a> для доступа к сети"
" из других языков (библиотека для C уже доступна, а для Python и Perl в "
"процессе разработки). Проект активно разрабатывается, и хоть ещё и не "
"href=\"%(sam)s\">простое, основанное на сокетах API</a> для доступа к "
"сети из других языков (библиотека для C уже доступна, а для Python и Perl"
" в процессе разработки). Проект активно разрабатывается, и хоть ещё и не "
"достиг стадии релиза 1.0, но текущий <a href=\"%(roadmap)s\">план "
"развития проекта</a> описывает дальнейший путь нашей команды."
@@ -697,7 +709,7 @@ msgstr ""
#: i2p2www/pages/site/about/media.html:8
#, python-format
msgid "To request an addition to this page, please send to %(email)s."
msgstr "Материалы для добавления на эту страницу отсылайте на %(email)s."
msgstr "Материалы для добавления на эту страницу отправляйте на %(email)s."
#: i2p2www/pages/site/about/media.html:11
msgid ""
@@ -772,7 +784,7 @@ msgid ""
"\"Hackers for Human Rights\".\n"
"<a href=\"%(mp3)s\">MP3 audio</a>"
msgstr ""
"НАВЕРНОЕ New York Июль 17, 2010 - Краткий обзор I2P от zzz, в конце "
"HOPE New York Июль 17, 2010 - Краткий обзор I2P от zzz, в конце "
"выступления Adrian Hong's\n"
"\"Хакеры за Права Человека\".\n"
"<a href=\"%(mp3)s\">MP3 audio</a>"
@@ -871,7 +883,7 @@ msgid ""
"Toronto, August 15-16, 2015"
msgstr ""
"<a href=\"%(link)s\">I2PCon 2015</a>\n"
"Торонто, август 15-16, 2015"
"Торонто, 15-16 августа 2015"
#: i2p2www/pages/site/about/media.html:105
#, python-format
@@ -923,7 +935,7 @@ msgid ""
"<a href=\"%(link2)s\">(webm)</a>\n"
"Andrew Savchenko (bircoph), FOSDEM, Brussel, February 4, 2018"
msgstr ""
"Проект невидимый интернет <a href=\"%(link)s\"></a>— Обзор и руководство\n"
"Проект Невидимый Интернет <a href=\"%(link)s\"></a>— Обзор и руководство\n"
"(mp4)\n"
"<a href=\"%(link2)s\">(webm)</a>\n"
"Андрей Савченко (bircoph), конференция FOSDEM, Брюссель, 4 февраля 2018"
@@ -997,7 +1009,7 @@ msgid ""
msgstr ""
"<a href=\"%(link)s\">Felix Atari объясняет основные принципы I2P</a>\n"
"(Youtube Video)\n"
"Felix Atari сотрудник Telecomix Crypto Munitions Bureau.\n"
"Felix Atari, сотрудник Telecomix Crypto Munitions Bureau.\n"
"Автор <a href=\"http://telecomix.org/\">Telecomix</a>"
#: i2p2www/pages/site/about/media.html:177
@@ -1009,8 +1021,8 @@ msgid ""
"This tutorial shows how to install and configure software needed to "
"access I2P."
msgstr ""
"<a href=\"%(link)s\">Как попасть в I2P, анонимный P2P Darknet (устновка в"
" Windows)</a>\n"
"<a href=\"%(link)s\">Как попасть в I2P, анонимный P2P Darknet (установка "
"в Windows)</a>\n"
"(Youtube Video)\n"
"Это руководство объяснит как установить и настроить ПО для доступа в I2P."
@@ -1097,8 +1109,8 @@ msgid ""
"(German)\n"
"November 2007."
msgstr ""
"<a href=\"%(link)s\">Netzwelt.de статья об анонимности в Интернет</a> (на"
" немецком), ноябрь 2007."
"<a href=\"%(link)s\">Netzwelt.de статья об анонимности в интернете</a> "
"(на немецком), ноябрь 2007."
#: i2p2www/pages/site/about/media.html:233
#, python-format
@@ -1239,8 +1251,8 @@ msgid ""
"network.\n"
"<a href=\"%(volunteer)s\">Get involved!</a>"
msgstr ""
"Мы маленькая группа людей, распределенная по нескольким континентам, мы "
"работаем над\n"
"Мы - маленькая группа людей, распределенная по нескольким континентам, мы"
" работаем над\n"
"продвижением различных частей проекта и обсуждаем архитектуру \n"
"сети.\n"
"<a href=\"%(volunteer)s\">Присоединяйтесь!</a>"
@@ -1263,7 +1275,7 @@ msgstr ""
#: i2p2www/pages/site/about/team.html:22
msgid "manage donations"
msgstr ""
msgstr "управлять пожертвованиями"
#: i2p2www/pages/site/about/team.html:25
msgid "PR manager"
@@ -1275,7 +1287,7 @@ msgstr "контакты с прессой, публичные отношени
#: i2p2www/pages/site/about/team.html:30
msgid "Compensation manager"
msgstr "менеждер по компенсациям"
msgstr "Менеджер по компенсациям"
#: i2p2www/pages/site/about/team.html:32
msgid "Compensation management"
@@ -1436,7 +1448,7 @@ msgstr ""
#: i2p2www/pages/site/about/team.html:130
msgid "Web Designer"
msgstr "Web-дизайнер"
msgstr "Веб-дизайнер"
#: i2p2www/pages/site/about/team.html:132
msgid "manage the public project website content design"
@@ -1600,7 +1612,7 @@ msgstr "Дистрибуция Debian/Ubuntu и поддержка PPA"
#: i2p2www/pages/site/about/team.html:247
msgid "Routerconsole backend and UI work, website revamp, unit tests work"
msgstr ""
"Бэкенд консоли маршрутизатора и работа на UI, исправления по веб-сайту, "
"Бэкэнд консоли маршрутизатора и работа на UI, исправления по веб-сайту, "
"юнит-тестирование"
#: i2p2www/pages/site/about/team.html:252
@@ -1613,7 +1625,7 @@ msgstr "Также помогали"
#: i2p2www/pages/site/about/team.html:258
msgid "I2PTunnel development, ministreaming library"
msgstr "Разработка I2PTunnel, библиотеки минипотоков"
msgstr "Разработка I2PTunnel, библиотеки мини-потоков"
#: i2p2www/pages/site/about/team.html:262
msgid "Project lead, Syndie lead"
@@ -1657,15 +1669,15 @@ msgstr "I2Phex (портирование Phex на I2P)"
#: i2p2www/pages/site/about/team.html:306
msgid "addressbook,i2p-bt,syndie client"
msgstr "адрессная книга, i2p-bt, клиент syndie"
msgstr "адресная книга, i2p-bt, клиент syndie"
#: i2p2www/pages/site/about/team.html:310
msgid "organize and develop the i2p-bt BitTorrent port"
msgstr "арганизация и разработка порта i2p-bt BitTorrent"
msgstr "организация и разработка порта i2p-bt BitTorrent"
#: i2p2www/pages/site/about/team.html:314
msgid "addressbook, i2p-bt, syndie client development"
msgstr "адрессная книга, i2p-bt, разработка клиента syndie"
msgstr "адресная книга, i2p-bt, разработка клиента syndie"
#: i2p2www/pages/site/about/team.html:318
msgid "encryption and signature routines, I2PIM"
@@ -1677,7 +1689,7 @@ msgstr "кодирование SAM jython, работа над stasher (DHT) и
#: i2p2www/pages/site/about/team.html:326
msgid "installer, systray, bogobot"
msgstr "инсталлятор, systray, bogobot"
msgstr "установщик, systray, bogobot"
#: i2p2www/pages/site/about/team.html:330
msgid "jbigi development, wiki migration, doc cleanup"
@@ -1705,7 +1717,7 @@ msgstr "документация. миграция wiki"
#: i2p2www/pages/site/about/team.html:354
msgid "translations into French"
msgstr "перевод на французкий"
msgstr "перевод на французский"
#: i2p2www/pages/site/about/team.html:358
msgid "C port of jcpuid"
@@ -1722,7 +1734,7 @@ msgstr "libSAM"
#: i2p2www/pages/site/about/team.html:370
#: i2p2www/pages/site/about/team.html:374
msgid "i2p-bt tracker development"
msgstr "разработка трэкера i2p-bt"
msgstr "разработка трекера i2p-bt"
#: i2p2www/pages/site/about/team.html:378
msgid "Console and website themes"
@@ -1742,11 +1754,11 @@ msgid ""
"discussions\n"
"about cryptography, anonymity and I2P-centric topics."
msgstr ""
"I2PCon 2015 первое мероприятие такого рода. Оно имеет две краткосрочные "
"I2PCon 2015 - первое мероприятие такого рода. У него две краткосрочные "
"цели.\n"
"Первое, это предоставить обычным людям площадку, на которой могут быть "
"Первая - предоставить обычным людям площадку, на которой могут быть "
"получены знания о приватности.\n"
"Второе, обеспечить I2P и его сообществу технические дискуссии\n"
"Вторая - обеспечить I2P и его сообществу технические дискуссии\n"
"о криптографии, анонимности и I2P."
#: i2p2www/pages/site/about/i2pcon/2015.html:15
@@ -1757,7 +1769,7 @@ msgid ""
"the importance of privacy, we wanted to provide a forum where this "
"community can grow."
msgstr ""
"Более крупная и долгосрочная цель построение\n"
"Более крупная и долгосрочная цель - построение\n"
"сообщества сознающих приватность индивидуалов. Связывая людей, осознающих"
" важность приватности, мы хотим предоставить форум для роста такого "
"сообщества."
@@ -1798,7 +1810,7 @@ msgid ""
"Note that in-I2P torrents may also be available on the clearnet due to "
"bridging by Vuze clients."
msgstr ""
"Обратите внимание на то, что I2P torrent-ы могут также быть доступны на "
"Обратите внимание на то, что I2P-torrent-ы могут также быть доступны на "
"clearnet из-за моста, образованного пользователями клиента Vuze."
#: i2p2www/pages/site/about/i2pcon/2015.html:50
@@ -1872,12 +1884,12 @@ msgid ""
"He recently left Deloitte to do consulting through his company The James "
"Group."
msgstr ""
"Lance James основатель Invisibile IRC Project, предшественника I2P, back "
"in 2002.\n"
"Lance James - основатель Invisibile IRC Project, предшественника I2P, "
"back in 2002.\n"
"Он основал свою собственную компанию по борьбе с киберугрозами в 2003.\n"
"Он фокусируется на защите сети, исследовании вредоносных программ, и "
"Он фокусируется на защите сети, исследовании вредоносных программ и "
"защите информации до сих пор.\n"
"В 2011-2013, он был директором Threat Intelligence в The Vigilant, "
"В 2011-2013 он был директором Threat Intelligence в The Vigilant, "
"поглощенной Deloitte в 2013.\n"
"Недавно он покинул Deloitte для консультирования через свою компанию The "
"James Group."
@@ -1896,12 +1908,12 @@ msgid ""
"He is also a contractor specializing in incident response.\n"
"His research areas include secure software development and data analytics."
msgstr ""
"Nicholas Johnston - профессор Информационной безопасности в Sheridan "
"Nicholas Johnston - профессор информационной безопасности в Sheridan "
"College's School of Applied Computing в программе подготовки бакалавров "
"по информационной безопасности \n"
"по информационной безопасности. \n"
"Его предыдущая профессиональная карьера была в цифровой судебной "
"экспертизе и расследованиях. \n"
"Он - также подрядчик, специализирующийся на реагировании на инциденты. \n"
"Он также подрядчик, специализирующийся на реагировании на инциденты. \n"
"Его области исследования включают безопасную разработку программного "
"обеспечения и аналитику данных."
@@ -1991,11 +2003,11 @@ msgid ""
msgstr ""
"Существует несколько основных применимых техник для увеличения видимой\n"
"производительности I2P - некоторые из них связаны с ЦП, другие связаны с\n"
"шириной канала, третьи связаны с протоколом. Тем не менее все они\n"
"шириной канала, третьи связаны с протоколом. Тем не менее, все они\n"
"оказывают влияние на задержки, пропускную способность и видимую "
"производительность\n"
"сети, так как снижают нагрузку на ограниченные ресурсы. Этот список, "
"конечно же\n"
"конечно же,\n"
"не является исчерпывающим, однако он охватывает основные доступные методы."
#: i2p2www/pages/site/about/performance/future.html:15
@@ -2027,11 +2039,11 @@ msgid ""
"ourselves to a <a href=\"%(sybilpdf)s\">Sybil</a> attack\n"
"from a powerful adversary with lots of fast machines."
msgstr ""
"Вероятно самым важным шагом к повышению производительности является\n"
"улучшение механизма выбора узлов через которые будет строиться тоннель,\n"
"Вероятно, самым важным шагом к повышению производительности является\n"
"улучшение механизма выбора узлов, через которые будет строиться туннель,\n"
"нужно удостовериться, что не будут использоваться слишком медленные узлы "
"или быстрые но \n"
"перегруженные узлы и т.д. В добавок к этому мы должны убедиться, что не "
"или быстрые, но \n"
"перегруженные узлы и т.д. Вдобавок к этому мы должны убедиться, что не "
"откроемся для атак типа <a href=\"%(sybilpdf)s\">Sybil</a>\n"
"со стороны сильных противников с множеством быстрых узлов."
@@ -2062,14 +2074,14 @@ msgstr ""
"для новых \n"
"узлов, провоцируя огромное количество сетевых сообщений и нагрузку на "
"маршрутизатор - мы \n"
"можем снизить или, даже, прекратить следить до тех пор пока мы не "
"можем снизить или даже прекратить следить до тех пор, пока мы не "
"обнаружим что-то \n"
"более плохое (например, снизить частоту слежения, основываясь на "
"последнем времени когда \n"
"последнем времени, когда \n"
"кто-то дал нам ссылку на кого-то, о ком мы раньше не знали). Также мы "
"можем оптимизировать \n"
"то, что мы на самом деле отправляем - сколько узлов участвует в отправке "
"(или, даже, \n"
"(или даже \n"
"в получении ответа), и сколько конкурентных поисков мы выполняем."
#: i2p2www/pages/site/about/performance/future.html:42
@@ -2100,14 +2112,14 @@ msgid ""
"a trivial AES operation."
msgstr ""
"Суть алгоритма <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> \n"
"состоит в управлении набором случайных одноразовых 32-байтных массивов, и"
" в удалении \n"
"состоит в управлении набором случайных одноразовых 32-байтных массивов и "
"в удалении \n"
"их, если они не были достаточно быстро использованы. Если мы удалим их "
"слишком рано, мы \n"
"перейдем к полному (дорогому) шифрованию ElGamal, но если мы не \n"
"удалим их достаточно быстро, нам придется уменьшить их количество, чтобы "
"не \n"
"исчерпать свободную память (и если получатель все таки поломается и "
"исчерпать свободную память (и если получатель все-таки поломается и "
"потеряет несколько \n"
"меток, то может возникнуть даже больше ошибок шифрования до обнаружения "
"этого). С более \n"
@@ -2151,7 +2163,7 @@ msgstr ""
"Сейчас наш алгоритм <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a>"
" \n"
"помечает каждое шифрованное сообщение уникальными случайными \n"
"32 байтами (\"метка сессии - session tag\"), определяющего, что сообщение"
"32 байтами (\"метка сессии - session tag\"), определяющими, что сообщение"
" было зашифровано \n"
"ассоциированным с сессией AES ключом. Это избавляет узлы от необходимости"
" помечать \n"
@@ -2162,7 +2174,7 @@ msgstr ""
"новым набором меток сессии вместе с шифрованным сообщением, прозрачно \n"
"предоставляя способ идентифицировать будущие сообщения. Далее мы должны "
"следить \n"
"за тем, какие сообщения были успешно доставлены, чтобы знать какие метки"
"за тем, какие сообщения были успешно доставлены, чтобы знать, какие метки"
" \n"
"мы можем использовать."
@@ -2186,8 +2198,8 @@ msgstr ""
"Это хорошо и довольно надежно работает, тем не менее, это не эффективно \n"
"с точки зрения использования пропускной способности, так как для этого "
"требуется досрочно доставлять \n"
"метки (и не все метки могут быть важны, некоторые могут быть бесполезны, "
"в связи с \n"
"метки (и не все метки могут быть важны, некоторые могут быть бесполезны в"
" связи с \n"
"их просрочкой). Хотя, в среднем, досрочная доставка метки сессии занимает"
" \n"
"32 байта на сообщение (размер метки). Хотя, как предложил Taral, этот \n"
@@ -2195,7 +2207,7 @@ msgstr ""
"PRNG - когда устанавливается новая сессия (через зашифрованный блок "
"ElGamal), \n"
"обе стороны используют PRNG и генерируют метки сессии по запросу \n"
"(и получатель предварительно рассчитывает следующие несколько значений, \n"
"(и получатель предварительно рассчитывает следующие несколько значений \n"
"для обработки очереди доставки)."
#: i2p2www/pages/site/about/performance/future.html:87
@@ -2233,12 +2245,12 @@ msgid ""
msgstr ""
"Это выглядит простым решением для высоконагруженных маршрутизаторов с "
"большой пропускной способностью, \n"
"но не должны на это рассчитывать до тех пор пока не оптимизируем алгоритм"
" построения туннеля. \n"
"но мы не должны на это рассчитывать до тех пор, пока не оптимизируем "
"алгоритм построения туннеля. \n"
"Тем не менее, 10 минутное время жизни туннеля жестко прописано в коде в "
"нескольких местах, \n"
"и для изменения длительности понадобятся значительные усилия. \n"
"Также, будет сложно обеспечить обратную совместимость такого изменения."
"Также будет сложно обеспечить обратную совместимость такого изменения."
#: i2p2www/pages/site/about/performance/future.html:102
msgid ""
@@ -2246,8 +2258,8 @@ msgid ""
"high,\n"
"there are no current plans to extend tunnel lifetime."
msgstr ""
"В настоящем, т.к. средняя частота удачного создания сетевого туннеля "
"довольно высока, \n"
"В настоящее время, т.к. средняя частота удачного создания сетевого "
"туннеля довольно высока, \n"
"мы не планируем увеличивать время жизни туннеля."
#: i2p2www/pages/site/about/performance/future.html:108
@@ -2275,7 +2287,7 @@ msgstr ""
"У нас есть еще одна довольно произвольная, но \"вполне подходящая\" вещь "
"- это \n"
"тайм-ауты на различные действия. Почему для \"peer unreachable\" у нас \n"
"тайм-аут 60 секунд, Почему мы пытаемся отправить извещения LeaseSet \n"
"тайм-аут 60 секунд? Почему мы пытаемся отправить извещения LeaseSet \n"
"через другой туннель спустя 10 секунд? Почему запрос к базе данных не "
"может \n"
"длиться дольше 60 или 20 секунд? Почему пункт назначения настроен на "
@@ -2338,7 +2350,7 @@ msgid ""
"Web controls and monitoring the health of the various streams, as well \n"
"as the ability to explicitly close or throttle them."
msgstr ""
"Веб управление и наблюдение за состоянием различных потоков, наряду с \n"
"Веб-управление и наблюдение за состоянием различных потоков, наряду с \n"
"возможностью явного их закрытия или уменьшения."
#: i2p2www/pages/site/about/performance/future.html:153
@@ -2366,9 +2378,9 @@ msgid ""
msgstr ""
"Заметные улучшения производительности были выполнены с использованием "
"нижеперечисленных техник.\n"
"Еще многое предстоит сделать, смотри на странице <a "
"Еще многое предстоит сделать, см. на странице <a "
"href=\"%(performance)s\">Производительность</a> \n"
"текущие вопросы и размышления"
"текущие вопросы и размышления."
#: i2p2www/pages/site/about/performance/history.html:10
msgid "Native math"
@@ -2431,13 +2443,13 @@ msgstr ""
"около \n"
"800&#37; прироста производительности шифрования и снижает нагрузку "
"наполовину. Это \n"
"было проверено только на одном компьютере пользователя, и оно уже готово "
"было проверено только на одном компьютере пользователя и оно уже готово "
"для \n"
"внедрения."
#: i2p2www/pages/site/about/performance/history.html:32
msgid "Garlic wrapping a \"reply\" LeaseSet"
msgstr "Garlic упаковка \"ответа\" LeaseSet"
msgstr "Чесночная упаковка \"ответа\" LeaseSet"
#: i2p2www/pages/site/about/performance/history.html:33
msgid "implemented but needs tuning"
@@ -2485,7 +2497,7 @@ msgid ""
msgstr ""
"Ранее, когда Alice отправила сообщение Bob'у, когда Bob отвечал, он был "
"вынужден \n"
"выполнить поиск в сетевой базе данных - отправляя несколько запросов "
"выполнить поиск в сетевой базе данных - отправляя несколько запросов, "
"чтобы добраться \n"
"до текущего LeaseSet Alice. Если у него уже есть текущий LeaseSet Alice, "
"он может вместо этого \n"
@@ -2516,9 +2528,9 @@ msgid ""
msgstr ""
"Для неопубликованных LeaseSets, таких как \"shared clients\", есть только"
" один способ \n"
"доставить LeaseSets Bob'у. К сожалению, это связывание каждый раз "
"доставить LeaseSets Бобу. К сожалению, это связывание каждый раз "
"добавляет \n"
"почти 100&#37; накладных расходов на высокоскоростное соединение, и "
"почти 100&#37; накладных расходов на высокоскоростное соединение и "
"гораздо больше \n"
"для соединений с меньшими сообщениями."
@@ -2529,8 +2541,8 @@ msgid ""
"\n"
"This will substantially reduce the total overhead of I2P messaging."
msgstr ""
"Изменения запланированные в релиз 0.6.2 будут отправлять LeaseSet только "
"при \n"
"Изменения, запланированные в релизе 0.6.2, будут отправлять LeaseSet "
"только при \n"
"необходимости, в начале соединения или когда изменится LeaseSet.\n"
"Это значительно уменьшит общие накладные расходы системы сообщений I2P."
@@ -2561,17 +2573,17 @@ msgstr ""
"В настоящий момент, все соединения TCP выполняют проверку валидности узла"
" после\n"
"выполнения полного (дорогого) алгоритма Диффи-Хеллмана обмена\n"
"приватными ключами сессии. Это означает, что если чьи то часы сильно "
"приватными ключами сессии. Это означает, что если чьи-то часы сильно "
"неточны, или\n"
"его NAT/firewall/и т.д. неверно сконфигурирован (или используется "
"несовместимая\n"
"версия роутера), эти клиенты постоянно (не совсем постоянно,\n"
"благодаря бан-листам) провоцируют бесполезные ресурсоемкие "
"криптографические\n"
"операции на всех узлах им известных. Хотя мы и хотим оставить некоторые \n"
"проверки внутри границ шифрования, мы так же хотим обновить\n"
"протокол так, что бы некоторые проверки выполнялись раньше и мы могли "
"отбросить не валидные соединения не тратя процессорное время и другие "
"операции на всех известных им узлах. Хотя мы и хотим оставить некоторые \n"
"проверки внутри границ шифрования, мы также хотим обновить\n"
"протокол так, чтобы некоторые проверки выполнялись раньше и мы могли "
"отбросить невалидные соединения, не тратя процессорное время и другие "
"ресурсы."
#: i2p2www/pages/site/about/performance/history.html:81
@@ -2626,7 +2638,7 @@ msgid ""
"increasing its window size as much as it could. By persisting with the \n"
"same selections for a given connection, the transfer rate is much faster."
msgstr ""
"Случайны выбор туннелей и сроков аренды для каждого сообщения создает "
"Случайный выбор туннелей и сроков аренды для каждого сообщения создает "
"большое количество \n"
"случаев доставки не-по-очереди, что мешает потоковой библиотеке \n"
"увеличивать размер ее окна до максимума. При сохранении \n"
@@ -2656,13 +2668,13 @@ msgid ""
msgstr ""
"Сообщения I2NP и их содержимое уже определены и имеют довольно \n"
"компактную структуру, хотя один атрибут структуры RouterInfo не \n"
"\"настраиваемый\" - это соответствие имя = значение в виде ASCII. Сейчас,"
" мы заполняем ее \n"
"\"настраиваемый\" - это соответствие имя = значение в виде ASCII. Сейчас "
"мы заполняем ее \n"
"публичной статистикой - около 3300 байт на узел. Простое \n"
"применение сжатия GZip позволит сократить ее размер до 1/3, и когда вы \n"
"поймете как часто структуры RouterInfo передаются по сети, вы увидите что"
" \n"
"это будет значительным выигрышем - каждый раз когда маршрутизатор "
"поймете, как часто структуры RouterInfo передаются по сети, вы увидите, "
"что \n"
"это будет значительным выигрышем - каждый раз, когда маршрутизатор "
"запрашивает у другого содержимое \n"
"сетевой БД, которого нет у узла, он получает 3-10 записей RouterInfo."
@@ -2697,21 +2709,21 @@ msgid ""
"reduced to a pair of messages, instead of the "
"SYN+ACK+request+response+CLOSE."
msgstr ""
"Сейчас у библиотеки минипотоков mihi есть довольно простой потоковый "
"Сейчас у библиотеки мини-потоков mihi есть довольно простой потоковый "
"протокол \n"
"согласования - Alice отправляет Bob'у сообщение SYN, Bob отвечает "
"согласования - Alice отправляет Бобу сообщение SYN, Боб отвечает "
"сообщением ACK, затем \n"
"Alice и Bob обмениваются данными, до тех пор пока один из них не отправит"
" другому \n"
"сообщение CLOSE. Для длительных подключений (например, для IRC сервера),"
"Alice и Боб обмениваются данными до тех пор пока один из них не отправит "
"другому \n"
"сообщение CLOSE. Для длительных подключений (например, для IRC-сервера),"
" \n"
"эти издержки незначительны, но для некоторых простых ситуаций "
"запрос-ответ \n"
"(например, запрос/ответ HTTP), приходится отправлять вдвое больше "
"(например, запрос/ответ HTTP) приходится отправлять вдвое больше "
"сообщений, чем это \n"
"необходимо. Если, тем не менее, Alice комбинирует свою отправку с "
"сообщением SYN, \n"
"и Bob комбинирует его первый ответ с ACK - и, возможно, также включит "
"и Боб комбинирует его первый ответ с ACK - и, возможно, также включит "
"флаг CLOSE - \n"
"временные потоки, такие как запросы HTTP, могут быть сокращены \n"
"до пары сообщений, вместо SYN+ACK+запрос+ответ+CLOSE."
@@ -2736,15 +2748,15 @@ msgid ""
"target, the\n"
"ACK message is forwarded back to us [through tunnels, of course])."
msgstr ""
"Протокол минипотоков унаследовал преимущества плохого проектного решения"
"Протокол мини-потоков унаследовал преимущества плохого проектного решения"
" \n"
"клиентского протокола I2P (I2CP) - иллюстрация \"mode=GUARANTEED\", "
"позволяющая то, \n"
"что иначе было бы ненадежным, негарантированным, протокол на основе "
"сообщений \n"
"используюется для надежной, блокирующей операции (приоткрывая покров, оно"
" все равно остается \n"
"ненадежным и основанным на сообщениях, с гарантиями доставки, "
"используется для надежной, блокирующей операции (приоткрывая покров, оно "
"все равно остается \n"
"ненадежным и основанным на сообщениях с гарантиями доставки, "
"предоставляемыми маршрутизатором с помощью \n"
"чесночной маршрутизации данных с сообщением \"ACK\" внутри, так что когда"
" данные доходят до получателя, \n"
@@ -2767,9 +2779,9 @@ msgid ""
"the TCP layer - selective ACKs, congestion detection, nagle, etc."
msgstr ""
"Как я уже <a href=\"%(link)s\">сказал</a>, наличие \n"
"I2PTunnel (и библиотеки минипотоков) было наилучшим путем из всех "
"I2PTunnel (и библиотеки мини-потоков) было наилучшим путем из всех "
"возможных,\n"
"но доступен и более эффективный механизм. Когда мы выпиливаем \n"
"но уже доступны и более эффективные механизмы. Когда мы выпиливаем \n"
"функциональность \"mode=GUARANTEED\", мы в сущности оставляем себе \n"
"I2CP, который выглядит как анонимный уровень IP, и, т.о., мы сможем \n"
"реализовать в потоковой библиотеке преимущества архитектурного опыта \n"
@@ -2777,7 +2789,7 @@ msgstr ""
#: i2p2www/pages/site/about/performance/index.html:2
msgid "Performance"
msgstr "Производительноть"
msgstr "Производительность"
#: i2p2www/pages/site/about/performance/index.html:5
msgid ""
@@ -2797,13 +2809,13 @@ msgid ""
" a most\n"
"emphatic <b>yes</b>."
msgstr ""
"Вероятно один и самых часто задаваемых вопросов это \"насколько быстра "
"Вероятно, один и самых часто задаваемых вопросов это \"насколько быстра "
"I2P?\", \n"
"и похоже никому не нравится ответ - \"это зависит\". После опробования "
"I2P, \n"
"и, похоже, никому не нравится ответ - \"это зависит\". После опробования "
"I2P \n"
"следующим вопросом становится \"а быстрее будет?\", и ответом на это "
"служит \n"
"самое решительно <b>да</b>."
"самое решительное <b>да</b>."
#: i2p2www/pages/site/about/performance/index.html:14
msgid ""
@@ -2823,18 +2835,18 @@ msgid ""
"other routers could be under load just as one router tests, but be free "
"if the second router tests."
msgstr ""
"I2P это полностью динамическая сеть. Каждый клиент известен другим узлам,"
" и проверяет локальные известные узлы на доступность и "
"I2P - это полностью динамическая сеть. Каждый клиент известен другим "
"узлам, и проверяет локальные известные узлы на доступность и "
"производительность. \n"
"Только доступные и производительные узлы добавляются в локальную NetDB (В"
" основном это только часть сети, около 500-1000).\n"
"Когда I2P строит туннели, она выбирает лучший ресурс из этого пула. "
"Например, только маленький набор из 20-50 узлов доступен для постройки "
"туннелей к ним.\n"
"Из-за того что проверки выполняются каждую минуту, пул используемых узлов"
" изменяется каждую минуту.\n"
"Каждым узлам I2P известны различные части сети, т.о. каждый маршрутизатор"
" имеет свой набор узлов I2P для туннелей.\n"
"Из-за того, что проверки выполняются каждую минуту, пул используемых "
"узлов изменяется каждую минуту.\n"
"Каждым узлам I2P известны различные части сети, т.о., каждый "
"маршрутизатор имеет свой набор узлов I2P для туннелей.\n"
"Даже если два маршрутизатора имеют одинаковый набор известных узлов, "
"проверка на доступность и производительность покажет, скорее всего, "
"различные результаты, т.к. другие маршрутизаторы могут быть под нагрузкой"
@@ -2851,12 +2863,12 @@ msgid ""
"And because every I2P node has different tunnels built, no two I2P nodes "
"have the same tunnel sets."
msgstr ""
"Описанное выше объясняет почему каждый узел I2P имеет отличный от других "
"набор узлов для постройки туннелей.\n"
"Из-за того что каждый узел I2P имеет свои задержки и полосу пропускания, "
"туннели (которые строятся через эти узлы) имеют различные значения "
"Описанное выше объясняет, почему каждый узел I2P имеет отличный от других"
" набор узлов для постройки туннелей.\n"
"Из-за того, что каждый узел I2P имеет свои задержки и полосу пропускания,"
" туннели (которые строятся через эти узлы) имеют различные значения "
"задержки и ширины канала.\n"
"И из-за того что каждый узел I2P строит свои туннели, нет ни одной пары "
"И из-за того, что каждый узел I2P строит свои туннели, нет ни одной пары "
"узлов I2P с одинаковым набором туннелей."
#: i2p2www/pages/site/about/performance/index.html:29
@@ -2903,7 +2915,7 @@ msgid ""
"latency and other limitations."
msgstr ""
"В большинстве случаев трафик в I2P (www, torrent, ...) нуждается в пакете"
" ack до отправки данных, необходимо дождаться пока пакет ack вернется с "
" ack до отправки данных, необходимо дождаться пока пакет ack вернется с "
"сервера.\n"
"В конце: отправка данных, дождаться ack, отправить еще данных, дождаться "
"ack, ...\n"
@@ -2911,7 +2923,7 @@ msgstr ""
"узле I2P и каждом соединении на этом пути, то обычно время получения "
"пакета ack обратно на клиенте составляет 1-3 секунды.\n"
"С некоторыми добавками транспортов TCP и I2P пакет данных имеет "
"ограничение на размер, и он не может быть таким большим как мы того "
"ограничение на размер и он не может быть таким большим, как мы того "
"хотим.\n"
"Вместе эти условия накладывают ограничение на максимальную пропускную "
"способность на туннель - 20-50 Кбайт/с.\n"
@@ -2937,8 +2949,8 @@ msgid ""
"loss of connection (ping timeout) or on when using eepget."
msgstr ""
"Из-за использования шифрования и других надстроек I2P (как то - "
"построение туннелей, задержки, ...) построение туннеля является "
"достаточно дорогим для времени CPU. \n"
"построение туннелей, задержки...) построение туннеля является достаточно "
"дорогим для времени CPU. \n"
"Вот почему пункту назначения разрешено иметь максимум 6 входящих и 6 "
"исходящих туннелей для передачи данных. С максимальной скоростью 50 кб/с "
"на туннель пункт назначения может \n"
@@ -2970,11 +2982,11 @@ msgstr ""
"назначения один узел I2P использует только ограниченный набор туннелей с "
"другими узлами I2P.\n"
"Например, если узел I2P это \"hop1\" и маленьком примере выше, то мы "
"видим только 1 участвующий туннель порожденный клиентом.\n"
"видим только 1 участвующий туннель, порожденный клиентом.\n"
"Если мы сложим всю сеть I2P, то сможем построить только ограниченное "
"число участвующих туннелей с ограниченной пропускной способностью.\n"
"Если кто-то предоставить это ограниченное число туннелей набору узлов "
"I2P, то только часть пропускной способности/мощности будет доступна для "
"Если кто-то предоставит это ограниченное число туннелей набору узлов I2P,"
" то только часть пропускной способности/мощности будет доступна для "
"использования."
#: i2p2www/pages/site/about/performance/index.html:73
@@ -2987,11 +2999,11 @@ msgid ""
"I2P attempts to spread the load across a lot of I2P nodes because of this"
" reason."
msgstr ""
"Чтобы остаться анонимным один маршрутизатор не должен быть использован "
"Чтобы остаться анонимным, один маршрутизатор не должен быть использован "
"всей сетью для построения туннелей.\n"
"Если один маршрутизатор выступает в качестве туннельного маршрутизатора "
"для ВСЕХ узлов I2P, то он становится как узким местом, так и центром "
"сбора адресов IP и данных от клиентов. Это не хорошо.\n"
"сбора адресов IP и данных от клиентов. Это не есть хорошо.\n"
"По этой причине I2P пытается распределить нагрузку на большое число узлов"
" I2P."
@@ -3008,7 +3020,7 @@ msgid ""
"This limits the amount of traffic routed across your I2P node as well."
msgstr ""
"Другая цель - это полносвязная сеть. Каждое соединение hop-hop использует"
" одно соединение TCP или UDP между узлами I2P. При 1000 соединений, видны"
" одно соединение TCP или UDP между узлами I2P. При 1000 соединений видны"
" \n"
"1000 соединений TCP. Это довольно много, и какой-нибудь домашний или "
"маленький офисный маршрутизатор (DSL, кабельный, ...) допускает только "
@@ -3032,8 +3044,8 @@ msgid ""
"will \n"
"be lower after a restart/shutdown for a minimum of 24h."
msgstr ""
"В общем, I2P очень сложна и нет простого способа выяснить почему ваш узел"
" не задействован.\n"
"В общем, I2P очень сложна и нет простого способа выяснить, почему ваш "
"узел не задействован.\n"
"Если ваш узел доступен в режиме 24/7 и имеет настройку доступной полосы "
"пропускания >128 Кбайт/с, он должен быть использован после передачи "
"некоторого количества трафика.\n"
@@ -3054,11 +3066,11 @@ msgid ""
"It will be faster if you use I2P and build more tunnels, e.g. use a "
"torrent or www for some time."
msgstr ""
"Также: другим узлам I2P должен быть известен ваш маршрутизатор I2P чтобы "
"иметь возможность проверять его доступность и производительность. "
"Требуется время для того чтобы ваш узел стал известен. \n"
"Также: другим узлам I2P должен быть известен ваш маршрутизатор I2P, чтобы"
" иметь возможность проверять его доступность и производительность. "
"Требуется время, чтобы ваш узел стал известен. \n"
"Оно станет быстрее, если вы используете I2P и строите больше туннелей, "
"например, используйте время от времени торрент или www."
"например, используете время от времени торрент или www."
#: i2p2www/pages/site/about/performance/index.html:99
msgid "Performance Improvements"
@@ -3070,6 +3082,6 @@ msgid ""
"For possible future performance improvements see\n"
"<a href=\"%(future)s\">Future Performance Improvements</a>."
msgstr ""
"Возможные будущие улучшения производительности смотри на странице \n"
"Возможные будущие улучшения производительности см. на странице \n"
"<a href=\"%(future)s\">Будущие Улучшения Производительности</a>."

11456
i2p2www/translations/uk/LC_MESSAGES/blog.po Normal file
View File

File diff suppressed because it is too large Load Diff

712
i2p2www/translations/uk/LC_MESSAGES/comparison.po Normal file
View File

@@ -0,0 +1,712 @@
# Ukrainian translations for I2P.
# Copyright (C) 2018 ORGANIZATION
# This file is distributed under the same license as the I2P project.
#
# Translators:
# Greg Koval <gregjsmith@gmx.com>, 2020
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-08-24 11:47+0000\n"
"PO-Revision-Date: 2020-07-23 01:57+0000\n"
"Last-Translator: Greg Koval <gregjsmith@gmx.com>\n"
"Language-Team: Ukrainian (Ukraine) "
"(http://www.transifex.com/otf/I2P/language/uk_UA/)\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 !="
" 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n "
"% 100 > 14) ? 1 : n % 1 == 0 && (n % 10 ==0 || (n % 10 >=5 && n % 10 <=9)"
" || (n % 100 >=11 && n % 100 <=14 )) ? 2: 3)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 1.3\n"
#: i2p2www/pages/site/comparison/freenet.html:2
msgid "I2P Compared to Freenet"
msgstr "I2P порівняно з Freenet"
#: i2p2www/pages/site/comparison/freenet.html:8
msgid ""
"Freenet is a fully distributed, peer to peer anonymous publishing "
"network, offering \n"
"secure ways to store data, as well as some approaches attempting to "
"address the loads\n"
"of a flash flood. While Freenet is designed as a distributed data store,"
" people have\n"
"built applications on top of it to do more generic anonymous "
"communication, such as \n"
"static websites and message boards."
msgstr ""
#: i2p2www/pages/site/comparison/freenet.html:16
#, python-format
msgid ""
"Compared to I2P, Freenet offers some substantial benefits - it is a "
"distributed data\n"
"store, while I2P is not, allowing people to retrieve the content "
"published by others \n"
"even when the publisher is no longer online. In addition, it should be "
"able to \n"
"distribute popular data fairly efficiently. I2P itself does not and will"
" not provide \n"
"this functionality. On the other hand, there is overlap for users who "
"simply want to \n"
"communicate with each other anonymously through websites, message boards,"
" file sharing\n"
"programs, etc. There have also been some attempts to develop a "
"distributed data \n"
"store to run on top of I2P,\n"
"(most recently a port of <a href=\"%(tahoe)s\">Tahoe-LAFS</a>)\n"
"but nothing is yet ready for general use."
msgstr ""
#: i2p2www/pages/site/comparison/freenet.html:29
msgid ""
"However, even ignoring any implementations issues, there are some "
"concerns \n"
"about Freenet's algorithms from both a scalability and anonymity "
"perspective, owing \n"
"largely to Freenet's heuristic driven routing. The interactions of "
"various techniques \n"
"certainly may successfully deter various attacks, and perhaps some "
"aspects of the \n"
"routing algorithms will provide the hoped for scalability. "
"Unfortunately, not much\n"
"analysis of the algorithms involved has resulted in positive results, but"
" there is still\n"
"hope. At the very least, Freenet does provide substantial anonymity "
"against an attacker\n"
"who does not have the resources necessary to analyze it further."
msgstr ""
#: i2p2www/pages/site/comparison/index.html:2
msgid "Comparing I2P to other projects"
msgstr "Порівняння I2P з інші проекти"
#: i2p2www/pages/site/comparison/index.html:4
msgid ""
"There are a great many other applications and projects working on "
"anonymous \n"
"communication and I2P has been inspired by much of their efforts. This "
"is not \n"
"a comprehensive list of anonymity resources - both freehaven's \n"
"<a href=\"http://freehaven.net/anonbib/topic.html\">Anonymity "
"Bibliography</a>\n"
"and GNUnet's <a href=\"https://www.gnunet.org/links/\">related "
"projects</a>\n"
"serve that purpose well. That said, a few systems stand out for further\n"
"comparison. The following have individual comparison pages:"
msgstr ""
#: i2p2www/pages/site/comparison/index.html:20
#, python-format
msgid ""
"The following are discussed on the <a href=\"%(othernetworks)s\">other "
"networks page:</a>"
msgstr ""
#: i2p2www/pages/site/comparison/index.html:33
#, python-format
msgid ""
"The content of this page is subject to update, discussion and dispute, "
"and we welcome comments and additions.\n"
"You may contribute an analysis by entering a <a href=\"%(trac)s\">new "
"ticket on Trac</a>."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:2
msgid "I2P Compared to Other Anonymous Networks"
msgstr "I2P порівняно з інші анонімні мережі"
#: i2p2www/pages/site/comparison/other-networks.html:5
msgid "The following networks are discussed on this page."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:17
#, python-format
msgid ""
"Most of the following sections are fairly old, and may not be accurate.\n"
"For an overview of available comparisons, see the\n"
"<a href=\"%(comparison)s\">main network comparisons page</a>.\n"
"You may contribute an analysis by entering a\n"
"<a href=\"%(trac)s\">new ticket on Trac</a>."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:29
#, python-format
msgid ""
"RetroShare is a set of peer-to-peer applications running in a\n"
"<a href=\"%(f2fwiki)s\">Friend-to-friend (F2F)</a> network. Each peer of "
"such F2F \n"
"network makes direct IP connections only to authenticated peers "
"(\"friends\") after explicit \n"
"certificates exchange. It can discover unauthenticated peers (e.g. "
"friends of friends), \n"
"but connections to them are relayed over \"friend\" peers for providing "
"privacy and anonymity."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:37
msgid ""
"RetroShare is designed to build a private network of trusted peers, while"
" I2P is designed \n"
"to be a large-scaled public anonymous network. Recent versions of "
"RetroShare have options to run \n"
"as a public \"darknet\" by using I2P or Tor as a transport. That way all "
"connections are \n"
"anonymized and no trust is required for adding new \"friends\"."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:48
#, python-format
msgid ""
"Morphmix and Tarzan are both fully distributed, peer to peer networks of"
" \n"
"anonymizing proxies, allowing people to tunnel out through the low "
"latency \n"
"mix network. Morphmix includes some very interesting collusion detection"
" \n"
"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of "
"IP\n"
"addresses to accomplish the same. The two primary differences between \n"
"these systems and I2P are related to I2P's <a "
"href=\"%(threatmodel)s\">threat model</a> \n"
"and their out-proxy design (as opposed to providing both sender and "
"receiver \n"
"anonymity). There is source code available to both systems, but we are "
"not aware \n"
"of their use outside of academic environments."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:172
#, python-format
msgid ""
"\n"
"Mixminion and Mixmaster are networks to support anonymous email against a"
" very\n"
"powerful adversary.\n"
"High-latency messaging applications running on top of I2P\n"
"(for example <a href=\"%(syndie)s\">Syndie</a> or I2PBote)\n"
"may perhaps prove adequate to meet the threat\n"
"model of those adversaries, while running in parallel along side the "
"needs of low latency users, to provide\n"
"a significantly larger anonymity set.\n"
"High-latency support within the I2P router itself may or may not be added"
" in a distant future release.\n"
"It is too early to say if I2P will meet the needs of users requiring "
"extreme protection for email."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:184
msgid ""
"As with Tor and Onion Routing, \n"
"both Mixminion and Mixmaster take the directory based approach as well."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:194
#, python-format
msgid ""
"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing "
"web requests,\n"
"and as such it has a few centralized nodes (participants in the cascade) "
"that blend\n"
"and mix requests from clients through the sequence of nodes (the cascade)"
" before \n"
"proxying out onto the web. The scope, threat model, and security is "
"substantially \n"
"different from I2P, but for those who don't require significant anonymity"
" but still\n"
"are not satisfied with an Anonymizer-like service, JAP is worth "
"reviewing. One\n"
"caution to note is that anyone under the jurisdiction of the German "
"courts may want\n"
"to take care, as the German Federal Bureau of Criminal Investigation "
"(FBCI) has \n"
"successfully mounted an \n"
"<a href=\"%(url)s\">attack</a> \n"
"on the network. Even though the method of this attack was later found to"
" be illegal \n"
"in the German courts, the fact that the data was successfully collected "
"is the \n"
"concern. Courts change their minds based upon circumstance, and this is "
"evidence that \n"
"if a government body or intelligence agency wanted to, they could gather "
"the data, even \n"
"if it may be found inadmissible in some courts later)"
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:216
#, python-format
msgid ""
"Both of these systems work through the same basic \n"
"<a href=\"%(antnet)s\">antnet</a> routing, providing some degree of\n"
"anonymity based on the threat model of providing plausible deniability "
"against a simple \n"
"non-colluding adversary. With the antnet routing, they first either do a"
" random walk or a \n"
"broadcast search to find some peer with the data or identity desired, and"
" then use a feedback\n"
"algorithm to optimize that found path. This works well for applications "
"that merely want to know \n"
"what other people around them have to offer - \"How are y'all doing\" vs."
" \"Hey Alice, how are you\" - \n"
"you basically get a local cluster of nodes that can share files with and "
"maintain some degree of \n"
"anonymity (though you don't have much control over who is in that group "
"of peers)."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:228
msgid ""
"However, the algorithm does not scale well at all - if the application "
"wants to speak with a \n"
"particular peer it ends up doing a broadcast search or random walk "
"(though if they are lucky enough\n"
"for that to succeed, the antnet routing should optimize that found "
"connection). This means that \n"
"while these networks can work great at small scales, they are not "
"suitable for large networks where\n"
"someone wants to get in touch with another specific peer. That does not "
"mean that there is no \n"
"value in these systems, just that their applicability is limited to "
"situations where their \n"
"particular issues can be addressed."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:239
#, python-format
msgid ""
"This was a closed-source network targeted at Iranian users.\n"
"Tor did a <a href=\"%(torpost)s\">good writeup on what to look for in a "
"circumvention tool</a>.\n"
"Suffice it to say that being closed source and publicly targeting a "
"specific country are not good ideas.\n"
"I2P is, of course, open source. However, that source, and our\n"
"<a href=\"%(docs)s\">technical documentation</a>, need much more review."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:248
msgid "Paid VPN Services"
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:249
#: i2p2www/pages/site/comparison/other-networks.html:255
#, python-format
msgid ""
"You may contribute an analysis by entering a\n"
"<a href=\"%(trac)s\">new ticket on Trac</a>."
msgstr ""
#: i2p2www/pages/site/comparison/other-networks.html:254
msgid "Others"
msgstr "Інші"
#: i2p2www/pages/site/comparison/tor.html:2
msgid "I2P Compared to Tor"
msgstr "I2P порівняно з Tor"
#: i2p2www/pages/site/comparison/tor.html:3
msgid "November 2016"
msgstr "Листопад 2016"
#: i2p2www/pages/site/comparison/tor.html:9
#, python-format
msgid ""
"Tor and Onion Routing are both anonymizing proxy networks, \n"
"allowing people to tunnel out through their low latency mix \n"
"network. The two primary differences between Tor / \n"
"Onion-Routing and I2P are again related to differences in \n"
"the threat model and the out-proxy design (though Tor\n"
"supports hidden services as well). In addition, Tor\n"
"takes the directory-based approach - providing a \n"
"centralized point to manage the overall 'view' of the \n"
"network, as well as gather and report statistics, as \n"
"opposed to I2P's distributed <a href=\"%(netdb)s\">network \n"
"database</a> and <a href=\"%(peerselection)s\">peer selection</a>."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:23
msgid ""
"The I2P/Tor outproxy functionality does have a few \n"
"substantial weaknesses against certain attackers - \n"
"once the communication leaves the mixnet, global passive\n"
"adversaries can more easily mount traffic analysis. In \n"
"addition, the outproxies have access to the cleartext \n"
"of the data transferred in both directions, and \n"
"outproxies are prone to abuse, along with all of the \n"
"other security issues we've come to know and love with \n"
"normal Internet traffic."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:35
msgid ""
"However, many people don't need to worry about those \n"
"situations, as they are outside their threat model. It\n"
"is, also, outside I2P's (formal) functional scope (if people want\n"
"to build outproxy functionality on top of an anonymous\n"
"communication layer, they can). In fact, some I2P users\n"
"currently take advantage of Tor to outproxy."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:49
msgid "Comparison of Tor and I2P Terminology"
msgstr "Порівняння термінології Tor та I2P"
#: i2p2www/pages/site/comparison/tor.html:50
msgid ""
"While Tor and I2P are similar in many ways, much of the terminology is "
"different."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:55
msgid "Cell"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:55
msgid "Message"
msgstr "Повідомлення"
#: i2p2www/pages/site/comparison/tor.html:56
msgid "Client"
msgstr "Клієнт"
#: i2p2www/pages/site/comparison/tor.html:56
msgid "Router or Client"
msgstr "Роутер або Клієнт"
#: i2p2www/pages/site/comparison/tor.html:57
msgid "Circuit"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:57
msgid "Tunnel"
msgstr "Тунель"
#: i2p2www/pages/site/comparison/tor.html:58
msgid "Directory"
msgstr "Директорія"
#: i2p2www/pages/site/comparison/tor.html:58
msgid "NetDb"
msgstr "NetDb"
#: i2p2www/pages/site/comparison/tor.html:59
msgid "Directory Server"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:59
msgid "Floodfill Router"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:60
msgid "Entry Guards"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:60
msgid "Fast Peers"
msgstr "Швидкісні піри"
#: i2p2www/pages/site/comparison/tor.html:61
msgid "Entry Node"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:61
msgid "Inproxy"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:62
msgid "Exit Node"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:62
msgid "Outproxy"
msgstr "Outproxy (зовнішній проксі)"
#: i2p2www/pages/site/comparison/tor.html:63
#: i2p2www/pages/site/comparison/tor.html:68
msgid "Hidden Service"
msgstr "Прихований сервіз"
#: i2p2www/pages/site/comparison/tor.html:63
#: i2p2www/pages/site/comparison/tor.html:68
msgid "Eepsite or Destination"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:64
msgid "Hidden Service Descriptor"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:64
msgid "LeaseSet"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:65
msgid "Introduction point"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:65
msgid "Inbound Gateway"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:66
msgid "Node"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:66
#: i2p2www/pages/site/comparison/tor.html:69
#: i2p2www/pages/site/comparison/tor.html:72
msgid "Router"
msgstr "Роутер"
#: i2p2www/pages/site/comparison/tor.html:67
msgid "Onion Proxy"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:67
msgid "I2PTunnel Client (more or less)"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:68
msgid "Onion Service"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:69
msgid "Relay"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:70
msgid "Rendezvous Point"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:70
msgid "somewhat like Inbound Gateway + Outbound Endpoint"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:71
msgid "Router Descriptor"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:71
msgid "RouterInfo"
msgstr "Інформація про роутера"
#: i2p2www/pages/site/comparison/tor.html:72
msgid "Server"
msgstr "Сервер"
#: i2p2www/pages/site/comparison/tor.html:75
msgid "Benefits of Tor over I2P"
msgstr "Переваги Tor над I2P"
#: i2p2www/pages/site/comparison/tor.html:78
msgid ""
"Much bigger user base; much more visibility in the academic and hacker "
"communities; benefits from\n"
"formal studies of anonymity, resistance, and performance;\n"
"has a non-anonymous, visible, university-based leader"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:84
msgid "Has already solved some scaling issues I2P has yet to address"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:85
msgid "Has significant funding"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:86
msgid "Has more developers, including several that are funded"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:88
msgid ""
"More resistant to state-level blocking due to TLS transport layer and "
"bridges\n"
"(I2P has proposals for \"full restricted routes\" but these are not yet "
"implemented)"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:93
msgid "Big enough that it has had to adapt to blocking and DOS attempts"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:94
msgid "Designed and optimized for exit traffic, with a large number of exit nodes"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:96
msgid ""
"Better documentation, has formal papers and specifications,\n"
"better website, many more translations"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:101
msgid "More efficient with memory usage"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:102
msgid "Tor client nodes have very low bandwidth overhead"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:104
msgid ""
"Centralized control reduces the complexity at each\n"
"node and can efficiently address Sybil attacks"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:110
msgid ""
"A core of high capacity nodes provides higher\n"
"throughput and lower latency"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:115
msgid "C, not Java (ewww)"
msgstr "C, не Java (ewww)"
#: i2p2www/pages/site/comparison/tor.html:118
msgid "Benefits of I2P over Tor"
msgstr "Переваги I2P над Tor"
#: i2p2www/pages/site/comparison/tor.html:120
msgid ""
"Designed and optimized for hidden services, which are much faster than in"
" Tor"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:121
msgid "Fully distributed and self organizing"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:123
msgid ""
"Peers are selected by continuously profiling and ranking performance,\n"
"rather than trusting claimed capacity"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:129
msgid ""
"Floodfill peers (\"directory servers\") are varying and untrusted,\n"
"rather than hardcoded"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:134
msgid "Small enough that it hasn't been blocked or DOSed much, or at all"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:135
msgid "Peer-to-peer friendly"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:136
msgid "Packet switched instead of circuit switched"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:139
msgid ""
"implicit transparent load balancing of messages \n"
"across multiple peers, rather than a single path"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:145
msgid ""
"resilience vs. failures by running multiple \n"
"tunnels in parallel, plus rotating tunnels"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:151
msgid ""
"scale each client's connections at O(1) instead \n"
"of O(N) (Alice has e.g. 2 inbound tunnels that are \n"
"used by all of the peers Alice is talking with, \n"
"rather than a circuit for each)"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:161
msgid ""
"Unidirectional tunnels instead of bidirectional\n"
"circuits, doubling the number of nodes a peer has to\n"
"compromise to get the same information."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:166
#, python-format
msgid "Counter-arguments and further discussion <a href=\"%(netdb)s\">here</a>."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:171
msgid ""
"Protection against detecting client activity, even\n"
"when an attacker is participating in the tunnel, as\n"
"tunnels are used for more than simply passing end \n"
"to end messages (e.g. netDb, tunnel management, \n"
"tunnel testing)"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:180
msgid ""
"Tunnels in I2P are short lived, decreasing the number\n"
"of samples that an attacker can use to mount an \n"
"active attack with, unlike circuits in Tor, which are\n"
"typically long lived."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:188
msgid ""
"I2P APIs are designed specifically for anonymity and\n"
"security, while SOCKS is designed for functionality."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:193
msgid "Essentially all peers participate in routing for others"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:195
msgid ""
"The bandwidth overhead of being a full peer is low, \n"
"while in Tor, while client nodes don't require much\n"
"bandwidth, they don't fully participate in the mixnet."
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:201
msgid "Integrated automatic update mechanism"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:202
msgid "Both TCP and UDP transports"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:203
msgid "Java, not C (ewww)"
msgstr "Java, не C (ewww)"
#: i2p2www/pages/site/comparison/tor.html:206
msgid "Other potential benefits of I2P but not yet implemented"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:207
msgid "...and may never be implemented, so don't count on them!"
msgstr "... і може ніколи не будуть реалізовані, тому не розраховуйте на них!"
#: i2p2www/pages/site/comparison/tor.html:210
msgid ""
"Defense vs. message count analysis by garlic wrapping \n"
"multiple messages"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:216
msgid ""
"Defense vs. long term intersection by adding delays \n"
"at various hops (where the delays are not discernible\n"
"by other hops)"
msgstr ""
#: i2p2www/pages/site/comparison/tor.html:223
msgid ""
"Various mixing strategies at the tunnel level (e.g.\n"
"create a tunnel that will handle 500 messages / minute,\n"
"where the endpoint will inject dummy messages if there\n"
"are insufficient messages, etc)"
msgstr ""

1236
i2p2www/translations/uk/LC_MESSAGES/misc.po Normal file
View File

File diff suppressed because it is too large Load Diff

766
i2p2www/translations/uk/LC_MESSAGES/research.po Normal file
View File

@@ -0,0 +1,766 @@
# Ukrainian translations for I2P.
# Copyright (C) 2018 ORGANIZATION
# This file is distributed under the same license as the I2P project.
#
# Translators:
# Greg Koval <gregjsmith@gmx.com>, 2020
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-06-24 13:48+0000\n"
"PO-Revision-Date: 2020-07-22 04:47+0000\n"
"Last-Translator: Greg Koval <gregjsmith@gmx.com>\n"
"Language-Team: Ukrainian (Ukraine) "
"(http://www.transifex.com/otf/I2P/language/uk_UA/)\n"
"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n % 10 == 1 && n % 100 !="
" 11 ? 0 : n % 1 == 0 && n % 10 >= 2 && n % 10 <= 4 && (n % 100 < 12 || n "
"% 100 > 14) ? 1 : n % 1 == 0 && (n % 10 ==0 || (n % 10 >=5 && n % 10 <=9)"
" || (n % 100 >=11 && n % 100 <=14 )) ? 2: 3)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 1.3\n"
#: i2p2www/pages/site/research/index.html:2
msgid "Academic Research"
msgstr "Наукові Дослідження"
#: i2p2www/pages/site/research/index.html:3
#: i2p2www/pages/site/research/questions.html:3
msgid "May 2018"
msgstr "Травень 2018"
#: i2p2www/pages/site/research/index.html:6
msgid "Introduction"
msgstr "Введення"
#: i2p2www/pages/site/research/index.html:8
msgid "Research on the I2P Network"
msgstr "Дослідження на мережі I2P"
#: i2p2www/pages/site/research/index.html:10
msgid ""
"I2P is a very unique project that unfortunately has not received the "
"wider\n"
"academic attention it deserves. To date, most research focus on anonymous"
" and\n"
"onion-routing technology has been around Tor, and while those papers "
"benefit us\n"
"as well, there is a great need for I2P-focused research. This plays a key"
" role\n"
"in both maintaining the security and integrity of the network, as well as"
"\n"
"opening doors for more impactful future development."
msgstr ""
#: i2p2www/pages/site/research/index.html:19
#, python-format
msgid ""
"\n"
"There is a large research community investigating a wide range of aspects"
" of\n"
"anonymity. For a current and comprehensive list of relevant papers, see "
"the\n"
"<a href=\"%(anonbib)s\">Free Haven Anonymity Bibliography</a>.\n"
"I2P benefits from much of the research into Tor and onion routing, but "
"there is\n"
"little dedicated research interest into the theory behind I2P, and the "
"choices\n"
"and tradeoffs that the network makes. This presents a unique opportunity "
"for\n"
"original research.\n"
msgstr ""
#: i2p2www/pages/site/research/index.html:29
#, python-format
msgid ""
"A list of known published papers about I2P is available <a "
"href=\"%(papers)s\">here</a>."
msgstr ""
#: i2p2www/pages/site/research/index.html:34
msgid ""
"\n"
"This page aims to outline the most needed fields of research, notes to\n"
"potential researchers, our general safety guidelines as well as an "
"expanding\n"
"list of open questions that you can begin on at any time.\n"
msgstr ""
#: i2p2www/pages/site/research/index.html:40
msgid "Notes to Researchers:"
msgstr "Нотатки для Дослідників:"
#: i2p2www/pages/site/research/index.html:42
msgid "Defensive Research"
msgstr ""
#: i2p2www/pages/site/research/index.html:44
msgid ""
"While all research on the I2P network is beneficial and appreciated, "
"there are\n"
"certain areas which are more in need than others - most so in defensive\n"
"research. Most people enjoy coming up with fun ways to launch offensives\n"
"against anonymous software, and this is further reinforced by the "
"incentives in\n"
"academic institutions. While we know it is often not the first choice for"
"\n"
"researchers, We would certainly appreciate any and all work towards ways "
"to\n"
"fortify the network!"
msgstr ""
#: i2p2www/pages/site/research/index.html:54
msgid "Offensive and Analytic Tests"
msgstr ""
#: i2p2www/pages/site/research/index.html:56
#, python-format
msgid ""
"If you've decided on a research topic that aims to hands-on investigate "
"the I2P\n"
"network or solve a problem of large proportions we ask you to "
"<b>please</b> \n"
"<a href=\"%(contact)s\">communicate your ideas</a> to the development "
"team, the\n"
"sooner the better. I2P is under constant development and a significant "
"amount\n"
"of roadmapping occurs, therefore your problem may have already been "
"identified\n"
"and flagged for update or patch. In the unlikely event you are conducting"
"\n"
"testing that overlaps with / would be of interest to another research "
"project\n"
"already in motion, we are also able to make you aware of this (with their"
"\n"
"permission, of course), and possibly open the door for collaboration. "
"There is\n"
"also a chance that the test itself may significantly harm the network or\n"
"regular users, and the team may have ideas or suggestions to mitigate "
"that risk\n"
"and increase the safety of your testing."
msgstr ""
#: i2p2www/pages/site/research/index.html:71
msgid "Research Ethics &amp; Testing the Network"
msgstr "Дослідження етики &amp; тестування мережі"
#: i2p2www/pages/site/research/index.html:73
msgid "General Guidelines"
msgstr "Загальні Рекомендації"
#: i2p2www/pages/site/research/index.html:75
msgid ""
"<ol>\n"
" <li>\n"
" Consider the benefits and risks - is there any doubt that the "
"research\n"
" provides more value than danger?\n"
" </li>\n"
" <li>\n"
" If the research can be done on a test network then that is the "
"preferred\n"
" method\n"
" </li>\n"
" <li>\n"
" If you must operate on the live network, the safest route is only\n"
" collecting data about yourself\n"
" </li>\n"
" <li>\n"
" If you need 'bigger data', It is recommended to first see if you can "
"use\n"
" data sets from previous experiments or other third party resources is"
"\n"
" recommended\n"
" </li>\n"
" <li>\n"
" If you must collect data on the live network, ensure it is safe for\n"
" publication and collect as little as possible\n"
" </li>\n"
" <li>\n"
" After testing and before publish, review that all data which is to be"
"\n"
" published publicly is <b><i>not</i></b> intended to be private by the"
"\n"
" originator\n"
" </li>\n"
"</ol>"
msgstr ""
#: i2p2www/pages/site/research/index.html:106
msgid "Using a Test Network to Attack I2P"
msgstr ""
#: i2p2www/pages/site/research/index.html:108
msgid ""
"I2P can be run as a separate test network by controlling the locations "
"that a\n"
"new router reseeds from so that it only finds other test routers.\n"
"\n"
"The standard mode of operation is to have one JVM per router instance; "
"hence\n"
"running multiple copies of I2P on a single machine is inadvisable, both "
"due to\n"
"the potential resource drain and the certain port conflicts. To better\n"
"facilitate setting up small test networks, I2P has a multirouter mode "
"which\n"
"enables multiple distinct routers to be run in the same JVM.\n"
"\n"
"MultiRouter can be started from the i2p base directory by running the "
"below\n"
"command."
msgstr ""
#: i2p2www/pages/site/research/index.html:124
msgid ""
"Additionally, I2P can be started in a virtual network mode. This mode "
"disables\n"
"all transports, allowing the router to be tested in isolation without "
"network\n"
"traffic. To enable this mode, add <code>i2p.vmCommSystem=true</code> to "
"the\n"
"router.config before starting."
msgstr ""
#: i2p2www/pages/site/research/index.html:131
msgid "Testing on the Live I2P Network"
msgstr ""
#: i2p2www/pages/site/research/index.html:133
#, python-format
msgid ""
"As stated above in the researcher notes, please <a "
"href=\"%(contact)s\">contact\n"
" us</a> before you commence your testing. While we do not discourage\n"
"researchers from responsibly testing their ideas on the live network, if "
"an\n"
"attack becomes apparent and we don't have any line of communication then "
"we\n"
"will end up taking countermeasures which could interfere with the test."
msgstr ""
#: i2p2www/pages/site/research/index.html:141
msgid "Router Family Configuration"
msgstr ""
#: i2p2www/pages/site/research/index.html:143
msgid ""
"As of release 0.9.25, I2P supports a router family configuration. This "
"provides\n"
"researchers who run multiple routers with the means to publicly identify "
"those\n"
"routers. In turn, this helps the I2P project understand that these "
"routers are\n"
"not running an attack on the network. It also will prevent other routers "
"from\n"
"including multiple routers of the family in a single tunnel, which could "
"lead\n"
"to deanonymization. Routers that appear to be colluding but do not have a"
"\n"
"declared family may be assumed to be an attack on the network, and may be"
"\n"
"blocked. The best way to ensure the success of your research project is "
"to work\n"
"with us directly."
msgstr ""
#: i2p2www/pages/site/research/index.html:155
msgid ""
"A router family shares a private key so that participation in the family "
"cannot\n"
"be spoofed. To configure a router family, click on the 'I2P Internals' "
"link in\n"
"the router console, and then on the 'Family' tab. Follow the instructions"
" there\n"
"to generate the private key for the first router in the family. Then, "
"export\n"
"the key from that router, and import it to other members of the family."
msgstr ""
#: i2p2www/pages/site/research/questions.html:2
msgid "Open research questions"
msgstr ""
#: i2p2www/pages/site/research/questions.html:5
msgid "Network database"
msgstr "Мережева база даних"
#: i2p2www/pages/site/research/questions.html:6
msgid "Floodfills"
msgstr ""
#: i2p2www/pages/site/research/questions.html:19
msgid "Transports"
msgstr "Транспорти"
#: i2p2www/pages/site/research/questions.html:31
msgid "Tunnels and Destinations"
msgstr ""
#: i2p2www/pages/site/research/questions.html:33
msgid "Peer selection"
msgstr ""
#: i2p2www/pages/site/research/questions.html:46
msgid "Unidirectional tunnels"
msgstr ""
#: i2p2www/pages/site/research/questions.html:52
msgid "Multihoming"
msgstr ""
#: i2p2www/pages/site/research/questions.html:59
msgid "Message routing"
msgstr ""
#: i2p2www/pages/site/research/questions.html:66
msgid "Anonymity"
msgstr "Анонімність"
#: i2p2www/pages/site/research/questions.html:75
msgid "Network Related"
msgstr "Пов'язані з мережею"
#: i2p2www/pages/site/research/vrp.html:2
msgid "Vulnerability Response Process"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:3
msgid "January 2017"
msgstr "Січень 2017"
#: i2p2www/pages/site/research/vrp.html:6
msgid ""
"\n"
"This process is subject to change. Please refer to this page for the "
"current VRP."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:10
msgid "Point of Contact for Security Issues"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:14
msgid "Security Response Team"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:16
msgid "Only the following members have access to the security point of contact:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:25
msgid "Incident Response"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:28
msgid "Researcher submits report via one or both of two methods:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:32
msgid "Email"
msgstr "Пошта"
#: i2p2www/pages/site/research/vrp.html:37
msgid ""
"Response Team designates a Response Manager who is in charge of the "
"particular\n"
"report based on availability and/or knowledge-set."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:42
#, python-format
msgid ""
"In no more than %(limit)s working days, Response Team should gratefully\n"
"respond to researcher using only encrypted methods."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:47
msgid ""
"Response Manager makes inquiries to satisfy any needed information and to"
"\n"
"confirm if submission is indeed a vulnerability."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:52
msgid "If submission proves to be vulnerable, proceed."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:55
msgid "If not vulnerable:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:59
msgid ""
"Response Manager responds with reasons why submission is not a "
"vulnerability."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:62
msgid ""
"Response Manager moves discussion to a new or existing ticket on public "
"Trac if necessary."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:70
msgid ""
"If over email, Response Manager opens a HackerOne issue for new "
"submission."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:74
msgid ""
"\n"
"Establish severity of vulnerability:\n"
" "
msgstr ""
#: i2p2www/pages/site/research/vrp.html:79
msgid ""
"Effects network as a whole, has potential to break entire network or is "
"on a scale of great catastrophe."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:83
msgid "Effects individual routers, or must be carefully exploited."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:87
msgid "Is not easily exploitable."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:93
msgid "Respond according to the severity of the vulnerability:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:97
#, python-format
msgid ""
"HIGH severities must be notified on website and news feed within "
"%(limit)s\n"
"working days of classification."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:102
msgid "The notification should list appropriate steps for users to take, if any."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:105
msgid ""
"The notification must not include any details that could suggest an "
"exploitation\n"
"path."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:109
msgid "The latter takes precedence over the former."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:113
msgid "MEDIUM and HIGH severities will require a Point Release."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:116
msgid "LOW severities will be addressed in the next Regular Release."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:122
msgid "Response Team applies appropriate patch(es)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:126
msgid ""
"Response Manager designates a PRIVATE monotone \"hotfix branch\" to work "
"in."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:129
msgid "Patches are reviewed with the researcher."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:132
msgid ""
"Any messages associated with PUBLIC commits during the time of review "
"should not\n"
"make reference to the security nature of the PRIVATE branch or its "
"commits."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:136
msgid "Vulnerability announcement is drafted."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:140
msgid "Include severity of vulnerability."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:143
msgid "Include systems/apps effected."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:146
msgid "Include solutions (if any) if patch cannot be applied."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:150
msgid "Release date is discussed."
msgstr "Обговорюється дата для реліз."
#: i2p2www/pages/site/research/vrp.html:156
msgid ""
"At release date, Response Team coordinates with developers to finalize "
"update:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:160
msgid "Response Manager propagates the \"hotfix branch\" to trunk."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:163
msgid ""
"Response Manager includes vulnerability announcement draft in release "
"notes."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:166
msgid "Proceed with the Point or Regular Release."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:173
msgid "Post-release Disclosure Process"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:176
#, python-format
msgid "Response Team has %(limit)s days to fulfill all points within section III."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:180
msgid "If the Incident Response process in section III is successfully completed:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:184
msgid ""
"Response Manager contacts researcher and asks if researcher wishes for "
"credit."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:187
msgid "Finalize vulnerability announcement draft and include the following:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:191
msgid "Project name and URL."
msgstr "Назва проекту та URL."
#: i2p2www/pages/site/research/vrp.html:194
msgid "Versions known to be affected."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:197
msgid ""
"Versions known to be not affected (for example, the vulnerable code was "
"introduced in a recent version, and older versions are therefore "
"unaffected)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:200
msgid "Versions not checked."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:203
msgid "Type of vulnerability and its impact."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:206
msgid "If already obtained or applicable, a CVE-ID."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:209
msgid "The planned, coordinated release date."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:212
msgid ""
"Mitigating factors (for example, the vulnerability is only exposed in "
"uncommon, non-default configurations)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:215
msgid ""
"Workarounds (configuration changes users can make to reduce their "
"exposure to the vulnerability)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:218
msgid "If applicable, credits to the original reporter."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:223
msgid "Release finalized vulnerability announcement on website and in news feed."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:226
msgid ""
"For HIGH severities, release finalized vulnerability announcement on "
"well-known mailing lists:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:234
msgid "If applicable, developers request a CVE-ID."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:238
msgid ""
"The commit that applied the fix is made reference too in a future commit "
"and includes a CVE-ID."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:246
msgid ""
"If the Incident Response process in section III is *not* successfully "
"completed:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:250
msgid ""
"Response Team and developers organize an IRC meeting to discuss why/what "
"points\n"
"in section III were not resolved and how the team can resolve them in the"
"\n"
"future."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:255
msgid ""
"Any developer meetings immediately following the incident should include "
"points\n"
"made in section V."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:259
msgid ""
"If disputes arise about whether or when to disclose information about a\n"
"vulnerability, the Response Team will publicly discuss the issue via IRC "
"and\n"
"attempt to reach consensus."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:264
#, python-format
msgid ""
"If consensus on a timely disclosure is not met (no later than %(limit)s "
"days),\n"
"the researcher (after %(limit)s days) has every right to expose the\n"
"vulnerability to the public."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:273
msgid "Incident Analysis"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:276
msgid "Isolate codebase"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:278
#: i2p2www/pages/site/research/vrp.html:298
msgid "Response Team and developers should coordinate to work on the following:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:282
msgid "Problematic implementation of classes/libraries/functions, etc."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:285
msgid "Focus on apps/distro packaging, etc."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:288
msgid "Operator/config error, etc."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:296
msgid "Auditing"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:302
msgid "Auditing of problem area(s) as discussed in point 1."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:305
msgid "Generate internal reports and store for future reference."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:308
msgid ""
"If results are not sensitive, share with the public via IRC or public "
"Trac."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:316
#, python-format
msgid ""
"Response Team has %(limit)s days following completion of section III to "
"ensure\n"
"completion of section V."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:322
msgid "Resolutions"
msgstr "Вирішення"
#: i2p2www/pages/site/research/vrp.html:324
msgid ""
"Any further questions or resolutions regarding the incident(s) between "
"the\n"
"researcher and response + development team after public disclosure can be"
"\n"
"addressed via the following:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:338
msgid "Continuous Improvement"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:341
msgid ""
"Response Team and developers should hold annual meetings to review the "
"previous\n"
"year's incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:346
msgid ""
"Response Team or designated person(s) should give a brief presentation, "
"including:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:350
msgid "Areas of I2P affected by the incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:353
msgid "Any network downtime or monetary cost (if any) of the incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:356
msgid "Ways in which the incidents could have been avoided (if any)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:359
msgid "How effective this process was in dealing with the incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:365
msgid "After the presentation, Response Team and developers should discuss:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:369
msgid "Potential changes to development processes to reduce future incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:372
msgid "Potential changes to this process to improve future responses."
msgstr ""

10
i2p2www/translations/zh/LC_MESSAGES/docs.po
View File

@@ -4,6 +4,7 @@
#
# Translators:
# ciaran <ciaranchen@qq.com>, 2019
# Nutr1t07 <nutr1t07@outlook.com>, 2020
# 黃彥儒 <r1235613@gmail.com>, 2015
# Scott Rhodes <starring169@gmail.com>, 2020
# YFdyh000 <yfdyh000@gmail.com>, 2016
@@ -13,8 +14,8 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-12-04 15:24+0000\n"
"PO-Revision-Date: 2020-03-28 05:44+0000\n"
"Last-Translator: Scott Rhodes <starring169@gmail.com>\n"
"PO-Revision-Date: 2020-11-14 08:42+0000\n"
"Last-Translator: Nutr1t07 <nutr1t07@outlook.com>\n"
"Language-Team: Chinese (China) "
"(http://www.transifex.com/otf/I2P/language/zh_CN/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
@@ -59,6 +60,9 @@ msgid ""
"If you find any inaccuracies in the documents linked below, please\n"
"<a href=\"%(trac)s\">enter a ticket identifying the problem</a>."
msgstr ""
"I2P项目致力于维护准确、时效性强的文档。\n"
"如果您在文档中发现任何不正确之处，请\n"
"<a href=\"%(trac)s\">提交该问题的描述</a>。"
#: i2p2www/pages/site/docs/index.html:26 i2p2www/pages/site/docs/naming.html:6
#: i2p2www/pages/site/docs/api/bob.html:30
@@ -382,7 +386,7 @@ msgstr ""
#: i2p2www/pages/site/docs/index.html:159
#: i2p2www/pages/site/docs/tunnels/unidirectional.html:2
msgid "Unidirectional Tunnels"
msgstr ""
msgstr "单向隧道"
#: i2p2www/pages/site/docs/index.html:160
#: i2p2www/pages/site/docs/how/peer-selection.html:299

28
i2p2www/translations/zh/LC_MESSAGES/research.po
View File

@@ -3,6 +3,7 @@
# This file is distributed under the same license as the I2P project.
#
# Translators:
# bright hong <heathcliff2333@outlook.com>, 2020
# xkimo_daeee <michael_ies@yahoo.com>, 2014
# Scott Rhodes <starring169@gmail.com>, 2020
# Tommy Lmath <l5h5t7@qq.com>, 2016
@@ -13,8 +14,8 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-06-24 13:48+0000\n"
"PO-Revision-Date: 2020-03-28 05:14+0000\n"
"Last-Translator: Scott Rhodes <starring169@gmail.com>\n"
"PO-Revision-Date: 2020-10-28 09:57+0000\n"
"Last-Translator: bright hong <heathcliff2333@outlook.com>\n"
"Language-Team: Chinese (China) "
"(http://www.transifex.com/otf/I2P/language/zh_CN/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
@@ -38,7 +39,7 @@ msgstr "介绍"
#: i2p2www/pages/site/research/index.html:8
msgid "Research on the I2P Network"
msgstr "I2P网络的研究"
msgstr "关于I2P网络的学术研究"
#: i2p2www/pages/site/research/index.html:10
msgid ""
@@ -53,7 +54,7 @@ msgid ""
"in both maintaining the security and integrity of the network, as well as"
"\n"
"opening doors for more impactful future development."
msgstr ""
msgstr "I2P是一个特别的项目，但它在学术圈没有得到应有的关注。目前，大多数关于匿名性和“洋葱”路由的研究都是围绕Tor进行的，尽管这些文章对我们也有帮助，我们仍认为需要有围绕I2P的研究。这在保持网络的安全性和正确性以及对于启示未来更有影响力的开发中扮演了重要角色。"
#: i2p2www/pages/site/research/index.html:19
#, python-format
@@ -73,9 +74,10 @@ msgid ""
"original research.\n"
msgstr ""
"\n"
"有一个调查匿名性方面范围广泛的大型研究社区 .当前综合有关论文列表，请参阅<a "
"href=\"%(anonbib)s\">自由避风港匿名参考书目</a>. I2P 得益于对 Tor 和裕 洋葱路由的大量研究. 不过, "
"对I2P后面的理论以及网络做出的选择和权衡的研究几乎没有. 这为原创研究提供了一个独特的条件.\n"
"有一个大型研究社区研究匿名性的方方面面。想寻找当前全面的论文列表，请参阅<a "
"href=\"%(anonbib)s\">自由避风港匿名参考文献Free Haven Anonymity Bibliography</a>。\n"
"I2P 得益于大量对 Tor 和洋葱路由的研究。但是，对I2P背后的理论以及网络做出的选择和权衡的研究几乎没有。这为原创研究提供了一个独特的机会。"
"\n"
#: i2p2www/pages/site/research/index.html:29
#, python-format
@@ -92,14 +94,16 @@ msgid ""
"expanding\n"
"list of open questions that you can begin on at any time.\n"
msgstr ""
"\n"
"本页面希望概括出最急需的研究方面，对潜在研究人员的寄语，我们总的安全指导原则以及一堆你可以着手的开放性问题。\n"
#: i2p2www/pages/site/research/index.html:40
msgid "Notes to Researchers:"
msgstr ""
msgstr "对研究人员的寄语："
#: i2p2www/pages/site/research/index.html:42
msgid "Defensive Research"
msgstr ""
msgstr "防御性研究"
#: i2p2www/pages/site/research/index.html:44
msgid ""
@@ -114,11 +118,11 @@ msgid ""
"researchers, We would certainly appreciate any and all work towards ways "
"to\n"
"fortify the network!"
msgstr ""
msgstr "我们认为所有关于I2P网络的研究都是有用的，且欢迎这样的研究，尽管如此，其中一些领域的研究比起别的更急需--主要在于防御性研究。许多人享受着想出对匿名软件的花式攻击方法，这种状况又被学校的奖励机制助长。尽管我们知道这不是研究人员的第一选择，我们仍期盼任何能够帮助强化网络的工作。"
#: i2p2www/pages/site/research/index.html:54
msgid "Offensive and Analytic Tests"
msgstr ""
msgstr "攻性和分析测试"
#: i2p2www/pages/site/research/index.html:56
#, python-format
@@ -146,6 +150,8 @@ msgid ""
"that risk\n"
"and increase the safety of your testing."
msgstr ""
"如果您决定做一个关于I2P的课题，一步步分析I2P网络，或解决大问题时，我们<b>恳切希望</b>您能与我们的开发团队<a "
"href=\"%(contact)s\">交流您的想法</a>，越快越好。I2P在持续开发中，会有大量开发路线，所以您的问题可能已经被标记准备更新解决。极少数情况下您的测试可能与别的研究组重合，我们也会提前告诉您（当然了，在他们的允许下），或许能促成您与另一团队的合作。也有可能测试本身会严重损害网络或普通用户，开发团队会给您建议来减少风险，增加测试安全性。"
#: i2p2www/pages/site/research/index.html:71
msgid "Research Ethics &amp; Testing the Network"

6
i2p2www/translations/zh_TW/LC_MESSAGES/get-involved.po
View File

@@ -9,8 +9,8 @@ msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-11-24 14:26+0000\n"
"PO-Revision-Date: 2019-11-24 14:31+0000\n"
"Last-Translator: zzzi2p\n"
"PO-Revision-Date: 2020-11-01 10:02+0000\n"
"Last-Translator: manjaro linux\n"
"Language-Team: Chinese (Taiwan) "
"(http://www.transifex.com/otf/I2P/language/zh_TW/)\n"
"Plural-Forms: nplurals=1; plural=0\n"
@@ -2763,7 +2763,7 @@ msgstr "翻譯"
#: i2p2www/pages/site/get-involved/guides/new-developers.html:17
#: i2p2www/pages/site/get-involved/guides/new-developers.html:198
msgid "Tools"
msgstr ""
msgstr "工具"
#: i2p2www/pages/site/get-involved/guides/new-developers.html:22
msgid ""

975
pots/about.pot
View File

File diff suppressed because it is too large Load Diff

996
pots/blog.pot
View File

File diff suppressed because it is too large Load Diff

6
pots/comparison.pot
View File

@@ -1,14 +1,14 @@
# Translations template for I2P.
# Copyright (C) 2018 ORGANIZATION
# Copyright (C) 2020 ORGANIZATION
# This file is distributed under the same license as the I2P project.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-08-24 11:47+0000\n"
"POT-Creation-Date: 2020-11-16 17:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

1727
pots/docs.pot
View File

File diff suppressed because it is too large Load Diff

170
pots/get-involved.pot
View File

@@ -1,14 +1,14 @@
# Translations template for I2P.
# Copyright (C) 2019 ORGANIZATION
# Copyright (C) 2020 ORGANIZATION
# This file is distributed under the same license as the I2P project.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2019.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2019-11-24 14:26+0000\n"
"POT-Creation-Date: 2020-11-16 17:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,6 +17,18 @@ msgstr ""
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 1.3\n"
#: i2p2www/pages/site/get-involved/bounties.html:2
msgid "Bounties"
msgstr ""
#: i2p2www/pages/site/get-involved/bounties.html:4
msgid ""
"Thank you for your interest in contributing to I2P!<br>\n"
"<br>\n"
"Currently there is no bounty system available.\n"
"<br>"
msgstr ""
#: i2p2www/pages/site/get-involved/donate.html:2
#: i2p2www/pages/site/get-involved/index.html:111
msgid "Donate"
@@ -357,56 +369,17 @@ msgid ""
"to security holes, benefit from ongoing research."
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2016.html:2
#: i2p2www/pages/site/get-involved/roadmap-2017.html:2
#: i2p2www/pages/site/get-involved/roadmap.html:2
msgid "Roadmap"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2016.html:3
msgid "January 2016"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2016.html:169
#: i2p2www/pages/site/get-involved/roadmap-2016.html:182
#: i2p2www/pages/site/get-involved/roadmap-2017.html:295
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2016.html:172
#: i2p2www/pages/site/get-involved/roadmap-2016.html:185
#: i2p2www/pages/site/get-involved/roadmap-2017.html:298
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2016.html:173
#: i2p2www/pages/site/get-involved/roadmap-2016.html:186
#: i2p2www/pages/site/get-involved/roadmap-2017.html:299
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2016.html:174
#: i2p2www/pages/site/get-involved/roadmap-2016.html:187
#: i2p2www/pages/site/get-involved/roadmap-2017.html:300
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2016.html:190
#: i2p2www/pages/site/get-involved/roadmap-2017.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:323
#: i2p2www/pages/site/get-involved/roadmap.html:215
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "
"about some of these tasks."
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap-2017.html:3
msgid "January 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/todo.html:2
msgid "I2P Project Targets"
msgstr ""
@@ -1572,14 +1545,6 @@ msgid ""
"<a href=\"%(licenseagreements)s\">See developers' license agreements</a>."
msgstr ""
#: i2p2www/pages/site/get-involved/develop/press-key.html:2
msgid "Press GPG Key"
msgstr ""
#: i2p2www/pages/site/get-involved/develop/press-key.html:4
msgid "Following is the GPG key for the press _at_ geti2p.net email address:"
msgstr ""
#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2
msgid "Release Signing Key"
msgstr ""
@@ -1772,7 +1737,7 @@ msgstr ""
msgid ""
"Please don't just \"write code\". If you can, participate in other "
"development activities, including:\n"
"development discussions and support on IRC, zzz.i2p, and forum.i2p; "
"development discussions and support on IRC, zzz.i2p, and i2pforum.i2p; "
"testing;\n"
"bug reporting and responses; documentation; code reviews; etc."
msgstr ""
@@ -1789,13 +1754,6 @@ msgstr ""
msgid "Release Cycle"
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:36
msgid ""
"Our normal release cycle is 6-10 weeks.\n"
"Following are the approximate deadlines within a typical 8-week cycle.\n"
"Actual deadlines for each release are set by the lead developer."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:43
msgid "1-2 days after previous release: Checkins to trunk are allowed."
msgstr ""
@@ -1820,31 +1778,6 @@ msgid ""
"link requests, if any."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:58
msgid ""
"7-10 days before release: String freeze. No more changes to translated "
"(\"tagged\") strings.\n"
"Push strings to Transifex, announce translation deadline on Transifex."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:62
msgid ""
"7-10 days before release: Feature deadline. Bug fixes only after this "
"time. No more features, refactoring or cleanup."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:65
msgid ""
"3-4 days before release: Translation deadline. Pull translations from "
"Transifex and check in."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68
msgid ""
"2-3 days before release: Checkin deadline. No checkins after this time "
"without the permission of the release builder."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:71
msgid "Hours before release: Code review deadline."
msgstr ""
@@ -1934,7 +1867,7 @@ msgstr ""
msgid ""
"For any Javadocs added, there must not be any doclint errors or warnings."
"\n"
"Run 'ant javadoc' with Oracle Java 8 or higher to check.\n"
"Run 'ant javadoc' with Oracle Java 14 or higher to check.\n"
"All params must have @param lines, all non-void methods must have @return"
" lines,\n"
"all exceptions declared thrown must have @throws lines, and no HTML "
@@ -1976,63 +1909,50 @@ msgid ""
"Run 'ant findbugs' to learn more."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:160
msgid ""
"We require Java 7 to build and run I2P.\n"
"Do not use Java 8 classes or methods anywhere.\n"
"Do not use Java 7 or 8 classes or methods in embedded subsystems (core, "
"router, mstreaming, streaming, i2ptunnel),\n"
"as Android and embedded applications require only Java 6. All classes "
"must be available in Android API 14.\n"
"Java 7 language features are acceptable in these subsystems if supported "
"by the current version\n"
"of the Android SDK and they compile to Java 6-compatible code."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:179
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:184
msgid ""
"Explicitly convert between primitive types and classes;\n"
"don't rely on autoboxing/unboxing."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:183
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:188
msgid "Don't use URL. Use URI."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:186
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:191
msgid ""
"Don't catch Exception. Catch RuntimeException and checked exceptions "
"individually."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:189
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:194
msgid ""
"Don't use String.getBytes() without a UTF-8 charset argument. You may "
"also use DataHelper.getUTF8() or DataHelper.getASCII()."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:192
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:197
msgid ""
"Always specify a UTF-8 charset when reading or writing files. The "
"DataHelper utilities may be helpful."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:195
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:200
msgid ""
"Always specify a locale (for example Locale.US) when using "
"String.toLowerCase() or String.toUpperCase().\n"
"Do not use String.equalsIgnoreCase(), as a locale cannot be specified."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:199
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:204
msgid "Don't use String.split(). Use DataHelper.split()."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:205
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:210
msgid "Ensure that InputStreams and OutputStreams are closed in finally blocks."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:208
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:213
msgid ""
"Use {} for all for and while blocks, even if only one line.\n"
"If you use {} for either the if, else, or if-else block, use it for all "
@@ -2040,25 +1960,25 @@ msgid ""
"Put \"} else {\" on a single line."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:213
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:218
msgid "Specify fields as final wherever possible."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:216
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:221
msgid ""
"Don't store I2PAppContext, RouterContext, Log, or any other references to"
" router or context items in static fields."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:219
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:224
msgid "Don't start threads in constructors. Use I2PAppThread instead of Thread."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:224
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:229
msgid "Licenses"
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:226
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:231
msgid ""
"Only check in code that you wrote yourself.\n"
"Before checking in any code or library jars from other sources,\n"
@@ -2067,7 +1987,7 @@ msgid ""
"and obtain approval from the lead developer."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:233
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:238
msgid ""
"If you do obtain approval to add external code or jars,\n"
"and binaries are available in any Debian or Ubuntu package,\n"
@@ -2076,18 +1996,18 @@ msgid ""
"Checklist of files to modify:"
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:241
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:246
msgid ""
"For any images checked in from external sources,\n"
"it is your responsibility to first verify the license is compatible.\n"
"Include the license and source information in the checkin comment."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:248
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:253
msgid "Bugs"
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:250
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:255
#, python-format
msgid ""
"Managing Trac tickets is everybody's job, please help.\n"
@@ -2095,7 +2015,7 @@ msgid ""
"Assign, categorize, comment on, fix, or close tickets if you can."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:255
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:260
msgid ""
"New developers should start by fixing a bug.\n"
"Search for bugs with the 'easy' keyword on trac.\n"
@@ -2107,7 +2027,7 @@ msgid ""
"the normal procedure below."
msgstr ""
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:262
#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:267
msgid ""
"Close a ticket when you think you've fixed it.\n"
"We don't have a test department to verify and close tickets.\n"
@@ -3340,10 +3260,6 @@ msgstr ""
msgid "How to Set up a Reseed Server"
msgstr ""
#: i2p2www/pages/site/get-involved/guides/reseed.html:3
msgid "February 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/guides/reseed.html:6
msgid "Overview"
msgstr ""
@@ -3454,9 +3370,7 @@ msgid ""
msgstr ""
#: i2p2www/pages/site/get-involved/guides/reseed.html:72
msgid ""
"If you would like to discuss support, please contact echelon and CC: "
"backup."
msgid "If you would like to discuss support, please contact echelon and CC: zzz"
msgstr ""
#: i2p2www/pages/site/get-involved/guides/reseed.html:77
@@ -3465,8 +3379,8 @@ msgstr ""
#: i2p2www/pages/site/get-involved/guides/reseed.html:79
msgid ""
"Our reseed coordinator is \"backup\" and he may be contacted at backup at"
" mail.i2p or backup at i2pmail.org.\n"
"Our reseed coordinator is \"zzz\" and he may be contacted at zzz at "
"mail.i2p or zzz at i2pmail.org.\n"
"Unfortunately, he is not generally on IRC. The reseed setup is somewhat "
"specialized, and you should direct most questions to him."
msgstr ""
@@ -3486,7 +3400,7 @@ msgstr ""
#: i2p2www/pages/site/get-involved/guides/reseed.html:95
msgid ""
"For further information, read the information at the following links, and"
" then contact backup.\n"
" then contact zzz.\n"
"Thank you!"
msgstr ""

6
pots/misc.pot
View File

@@ -1,14 +1,14 @@
# Translations template for I2P.
# Copyright (C) 2018 ORGANIZATION
# Copyright (C) 2020 ORGANIZATION
# This file is distributed under the same license as the I2P project.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-02-12 00:06+0000\n"
"POT-Creation-Date: 2020-11-16 17:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"

1211
pots/priority.pot
View File

File diff suppressed because it is too large Load Diff

221
pots/research.pot
View File

@@ -1,14 +1,14 @@
# Translations template for I2P.
# Copyright (C) 2018 ORGANIZATION
# Copyright (C) 2020 ORGANIZATION
# This file is distributed under the same license as the I2P project.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2018-06-24 13:48+0000\n"
"POT-Creation-Date: 2020-11-16 17:04+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -321,10 +321,6 @@ msgstr ""
msgid "Vulnerability Response Process"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:3
msgid "January 2017"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:6
msgid ""
"\n"
@@ -333,27 +329,49 @@ msgid ""
msgstr ""
#: i2p2www/pages/site/research/vrp.html:10
msgid "This page was last updated in June 2020."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:12
msgid ""
"Researchers: while you research/hack, we ask that you refrain from the "
"following: - Performing active exploits or Denial of Service attacks on "
"the\n"
"i2p network - Performing social engineering on i2p development team "
"members - Performing any physical or electronic attempts against i2p "
"property and/or data\n"
"centers"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:15
msgid ""
"As i2p is an open-source community, many volunteers and development team "
"members run their own EepSites as well as public (“clearnet”) domains. "
"These\n"
"sites/servers are NOT in the scope of the vulnerability assessment / "
"response process, only the underlying code of i2p is."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:18
msgid "Point of Contact for Security Issues"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:14
#: i2p2www/pages/site/research/vrp.html:22
msgid "Security Response Team"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:16
msgid "Only the following members have access to the security point of contact:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:25
msgid "Incident Response"
#: i2p2www/pages/site/research/vrp.html:24
msgid ""
"Echelon is the trusted security point-of-contact. He forwards e-mails to "
"team members as appropriate."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:28
msgid "Researcher submits report via one or both of two methods:"
msgid "Incident Response"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:32
msgid "Email"
#: i2p2www/pages/site/research/vrp.html:31
msgid "Researcher submits report via:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:37
@@ -366,7 +384,7 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:42
#, python-format
msgid ""
"In no more than %(limit)s working days, Response Team should gratefully\n"
"In no more than %(limit)s working days, Response Team should\n"
"respond to researcher using only encrypted methods."
msgstr ""
@@ -399,36 +417,30 @@ msgstr ""
#: i2p2www/pages/site/research/vrp.html:70
msgid ""
"If over email, Response Manager opens a HackerOne issue for new "
"submission."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:74
msgid ""
"\n"
"Establish severity of vulnerability:\n"
" "
msgstr ""
#: i2p2www/pages/site/research/vrp.html:79
#: i2p2www/pages/site/research/vrp.html:75
msgid ""
"Effects network as a whole, has potential to break entire network or is "
"Affects network as a whole, has potential to break entire network or is "
"on a scale of great catastrophe."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:83
msgid "Effects individual routers, or must be carefully exploited."
#: i2p2www/pages/site/research/vrp.html:79
msgid "Affects individual routers, or must be carefully exploited."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:87
#: i2p2www/pages/site/research/vrp.html:83
msgid "Is not easily exploitable."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:93
#: i2p2www/pages/site/research/vrp.html:89
msgid "Respond according to the severity of the vulnerability:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:97
#: i2p2www/pages/site/research/vrp.html:93
#, python-format
msgid ""
"HIGH severities must be notified on website and news feed within "
@@ -436,44 +448,45 @@ msgid ""
"working days of classification."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:102
#: i2p2www/pages/site/research/vrp.html:98
msgid "The notification should list appropriate steps for users to take, if any."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:105
#: i2p2www/pages/site/research/vrp.html:101
msgid ""
"The notification must not include any details that could suggest an "
"exploitation\n"
"path."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:109
#: i2p2www/pages/site/research/vrp.html:105
msgid "The latter takes precedence over the former."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:113
#: i2p2www/pages/site/research/vrp.html:109
msgid "MEDIUM and HIGH severities will require a Point Release."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:116
#: i2p2www/pages/site/research/vrp.html:112
msgid "LOW severities will be addressed in the next Regular Release."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:122
#: i2p2www/pages/site/research/vrp.html:118
msgid "Response Team applies appropriate patch(es)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:126
#: i2p2www/pages/site/research/vrp.html:122
msgid ""
"Response Manager designates a PRIVATE monotone \"hotfix branch\" to work "
"in."
"Response Manager works on a patch LOCALLY, patches are shared by the "
"response team via PGP-encrypted e-mail until such a time as it is safe to"
" expose to the public."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:129
#: i2p2www/pages/site/research/vrp.html:125
msgid "Patches are reviewed with the researcher."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:132
#: i2p2www/pages/site/research/vrp.html:128
msgid ""
"Any messages associated with PUBLIC commits during the time of review "
"should not\n"
@@ -481,143 +494,151 @@ msgid ""
"commits."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:136
#: i2p2www/pages/site/research/vrp.html:132
msgid "Vulnerability announcement is drafted."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:140
#: i2p2www/pages/site/research/vrp.html:136
msgid "Include severity of vulnerability."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:143
#: i2p2www/pages/site/research/vrp.html:139
msgid "Include systems/apps effected."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:146
#: i2p2www/pages/site/research/vrp.html:142
msgid "Include solutions (if any) if patch cannot be applied."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:150
#: i2p2www/pages/site/research/vrp.html:146
msgid "Release date is discussed."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:156
#: i2p2www/pages/site/research/vrp.html:152
msgid ""
"At release date, Response Team coordinates with developers to finalize "
"update:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:160
#: i2p2www/pages/site/research/vrp.html:156
msgid "Response Manager propagates the \"hotfix branch\" to trunk."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:163
#: i2p2www/pages/site/research/vrp.html:159
msgid ""
"Response Manager includes vulnerability announcement draft in release "
"notes."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:166
msgid "Proceed with the Point or Regular Release."
#: i2p2www/pages/site/research/vrp.html:162
msgid ""
"Proceed with the Point or Regular Release. At this time, it is not "
"possible to release an in-network update for only one operating system or"
"\n"
"\t\tarchitecture. In order that all affected products can be released as "
"quickly as possible, the person responsible\n"
"\t\tfor that software should be able to perform necessary release "
"processes in a timely manner. Importantly this should include\n"
"\t\tconsideration for package maintainers in Debian, Ubuntu and F-Droid."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:173
#: i2p2www/pages/site/research/vrp.html:172
msgid "Post-release Disclosure Process"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:176
#: i2p2www/pages/site/research/vrp.html:175
#, python-format
msgid "Response Team has %(limit)s days to fulfill all points within section III."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:180
#: i2p2www/pages/site/research/vrp.html:179
msgid "If the Incident Response process in section III is successfully completed:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:184
#: i2p2www/pages/site/research/vrp.html:183
msgid ""
"Response Manager contacts researcher and asks if researcher wishes for "
"credit."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:187
#: i2p2www/pages/site/research/vrp.html:186
msgid "Finalize vulnerability announcement draft and include the following:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:191
#: i2p2www/pages/site/research/vrp.html:190
msgid "Project name and URL."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:194
#: i2p2www/pages/site/research/vrp.html:193
msgid "Versions known to be affected."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:197
#: i2p2www/pages/site/research/vrp.html:196
msgid ""
"Versions known to be not affected (for example, the vulnerable code was "
"introduced in a recent version, and older versions are therefore "
"unaffected)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:200
#: i2p2www/pages/site/research/vrp.html:199
msgid "Versions not checked."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:203
#: i2p2www/pages/site/research/vrp.html:202
msgid "Type of vulnerability and its impact."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:206
#: i2p2www/pages/site/research/vrp.html:205
msgid "If already obtained or applicable, a CVE-ID."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:209
#: i2p2www/pages/site/research/vrp.html:208
msgid "The planned, coordinated release date."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:212
#: i2p2www/pages/site/research/vrp.html:211
msgid ""
"Mitigating factors (for example, the vulnerability is only exposed in "
"uncommon, non-default configurations)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:215
#: i2p2www/pages/site/research/vrp.html:214
msgid ""
"Workarounds (configuration changes users can make to reduce their "
"exposure to the vulnerability)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:218
#: i2p2www/pages/site/research/vrp.html:217
msgid "If applicable, credits to the original reporter."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:223
#: i2p2www/pages/site/research/vrp.html:222
msgid "Release finalized vulnerability announcement on website and in news feed."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:226
#: i2p2www/pages/site/research/vrp.html:230
msgid ""
"For HIGH severities, release finalized vulnerability announcement on "
"well-known mailing lists:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:234
#: i2p2www/pages/site/research/vrp.html:238
msgid "If applicable, developers request a CVE-ID."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:238
#: i2p2www/pages/site/research/vrp.html:242
msgid ""
"The commit that applied the fix is made reference too in a future commit "
"and includes a CVE-ID."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:246
#: i2p2www/pages/site/research/vrp.html:250
msgid ""
"If the Incident Response process in section III is *not* successfully "
"completed:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:250
#: i2p2www/pages/site/research/vrp.html:254
msgid ""
"Response Team and developers organize an IRC meeting to discuss why/what "
"points\n"
@@ -626,14 +647,14 @@ msgid ""
"future."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:255
#: i2p2www/pages/site/research/vrp.html:259
msgid ""
"Any developer meetings immediately following the incident should include "
"points\n"
"made in section V."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:259
#: i2p2www/pages/site/research/vrp.html:263
msgid ""
"If disputes arise about whether or when to disclose information about a\n"
"vulnerability, the Response Team will publicly discuss the issue via IRC "
@@ -641,7 +662,7 @@ msgid ""
"attempt to reach consensus."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:264
#: i2p2www/pages/site/research/vrp.html:268
#, python-format
msgid ""
"If consensus on a timely disclosure is not met (no later than %(limit)s "
@@ -650,50 +671,50 @@ msgid ""
"vulnerability to the public."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:273
#: i2p2www/pages/site/research/vrp.html:277
msgid "Incident Analysis"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:276
#: i2p2www/pages/site/research/vrp.html:280
msgid "Isolate codebase"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:278
#: i2p2www/pages/site/research/vrp.html:298
#: i2p2www/pages/site/research/vrp.html:282
#: i2p2www/pages/site/research/vrp.html:302
msgid "Response Team and developers should coordinate to work on the following:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:282
#: i2p2www/pages/site/research/vrp.html:286
msgid "Problematic implementation of classes/libraries/functions, etc."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:285
#: i2p2www/pages/site/research/vrp.html:289
msgid "Focus on apps/distro packaging, etc."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:288
#: i2p2www/pages/site/research/vrp.html:292
msgid "Operator/config error, etc."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:296
#: i2p2www/pages/site/research/vrp.html:300
msgid "Auditing"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:302
#: i2p2www/pages/site/research/vrp.html:306
msgid "Auditing of problem area(s) as discussed in point 1."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:305
#: i2p2www/pages/site/research/vrp.html:309
msgid "Generate internal reports and store for future reference."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:308
#: i2p2www/pages/site/research/vrp.html:312
msgid ""
"If results are not sensitive, share with the public via IRC or public "
"Trac."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:316
#: i2p2www/pages/site/research/vrp.html:320
#, python-format
msgid ""
"Response Team has %(limit)s days following completion of section III to "
@@ -701,11 +722,11 @@ msgid ""
"completion of section V."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:322
#: i2p2www/pages/site/research/vrp.html:326
msgid "Resolutions"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:324
#: i2p2www/pages/site/research/vrp.html:328
msgid ""
"Any further questions or resolutions regarding the incident(s) between "
"the\n"
@@ -714,48 +735,48 @@ msgid ""
"addressed via the following:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:338
#: i2p2www/pages/site/research/vrp.html:341
msgid "Continuous Improvement"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:341
#: i2p2www/pages/site/research/vrp.html:344
msgid ""
"Response Team and developers should hold annual meetings to review the "
"previous\n"
"year's incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:346
#: i2p2www/pages/site/research/vrp.html:349
msgid ""
"Response Team or designated person(s) should give a brief presentation, "
"including:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:350
#: i2p2www/pages/site/research/vrp.html:353
msgid "Areas of I2P affected by the incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:353
#: i2p2www/pages/site/research/vrp.html:356
msgid "Any network downtime or monetary cost (if any) of the incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:356
#: i2p2www/pages/site/research/vrp.html:359
msgid "Ways in which the incidents could have been avoided (if any)."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:359
#: i2p2www/pages/site/research/vrp.html:362
msgid "How effective this process was in dealing with the incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:365
#: i2p2www/pages/site/research/vrp.html:368
msgid "After the presentation, Response Team and developers should discuss:"
msgstr ""
#: i2p2www/pages/site/research/vrp.html:369
#: i2p2www/pages/site/research/vrp.html:372
msgid "Potential changes to development processes to reduce future incidents."
msgstr ""
#: i2p2www/pages/site/research/vrp.html:372
#: i2p2www/pages/site/research/vrp.html:375
msgid "Potential changes to this process to improve future responses."
msgstr ""